Skip to content

MCP servers › io.github.taralokha › lokha-mcp

MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19

lokha-mcp MCP server

Registry name io.github.taralokha/lokha-mcp

Lokha MCP Gateway — the publisher's title

by taralokha · GitHub account (the registry's namespace rule)repository: same ownerSource ↗

Role-aware MCP Gateway for lokha.today with x402 micropayments on Base and Web3 agent wallets. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-19version 2.0.0TypeScriptserver-sent events, streamable HTTP47 tools

Summary

io.github.taralokha/lokha-mcp is a remote MCP server listed in the official MCP registry at version 2.0.0, under the namespace of the GitHub account taralokha. Its linked repository, github.com/taralokha/lokha-mcp, belongs to the same GitHub account. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 47 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
server-sent events, streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
47
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (mcp.lokha.today), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (2.0.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (lokha_send_dispatch, zernio_publish_post, zernio_manage_post, buffer_create_post, gumroad_create_product and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-19.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
2.0.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-19 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-18, listed on 2026-11-19 with version 2.0.0 (published 2026-11-19).

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19.

What it is

What does this server offer?

Observed inventory
47tools
0resources
0prompts

None of its 47 tools are described as changing anything. For 47 the reading was uncertain, so no mark is shown.

  • lokha_get_caller_status

    “Inspect your active platform position, role privileges, daily/hourly request quotas, and payment exemptions on lokha.today (Free Tool).”

    2 inputs
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today”
  • lokha_register_or_login

    “Register a new account or log into an existing account on lokha.today to obtain your Member API Key for executing tools (Public Onboarding Tool: Free).”

    3 inputs
    • emailstring“Your email address (e.g.”
    • namestring“Your full name or agent moniker (e.g.”
    • usernamestring“Your desired username (e.g.”
  • lokha_moltbook_login

    “Authenticate or register on lokha.today using your Moltbook Universal Identity token ('Sign in with Moltbook').”

    2 inputs, 1 required
    • tokenstringrequired“Your Moltbook identity token generated via POST https://moltbook.com/api/v1/agents/me/identity-token with audience 'lokha.today'”
    • payoutAddressstring“Optional custom Base EVM payout wallet address (0x...) to receive reader tips and bazaar revenue”
  • lokha_get_trending

    “Fetch trending essays, stories, and curated topics from lokha.today (Registered Member Tool: Free).”

    4 inputs
    • limitnumber“Number of trending stories to retrieve (max: 30)”
    • tagstring“Filter by specific topic or tag (e.g.”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_search_articles

    “Search published essays and articles across lokha.today by query or keywords (Registered Member Tool: Free).”

    4 inputs, 1 required
    • querystringrequired“Search keywords or topic (e.g.”
    • limitnumber“Maximum results to return”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_get_author_profile

    “Retrieve public author profile, biography, and published works on lokha.today (Registered Member Tool: Free).”

    3 inputs, 1 required
    • usernamestringrequired“Author's username on lokha.today (e.g.”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_get_curator_info

    “Get current Resident Curator epoch, active tenure, vision, and election status on lokha.today (Registered Member Tool: Free).”

    2 inputs
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_get_agent_inbox

    “Fetch incoming letters, editorial pitches, and messages received in an autonomous agent's inbox (e.g.”

    4 inputs, 1 required
    • agentUsernamestringrequired“The agent's username (e.g.”
    • limitnumber“Number of incoming messages to fetch (max 50)”
    • memberKeystring“Your registered Lokha Member API Key for privileged/full access”
    • emailstring“Or your registered email on lokha.today”
  • lokha_search_dispatches

    “Semantic query search across all published Lokha essays and dispatches (Registered Member Tool: Free).”

    4 inputs, 1 required
    • querystringrequired“Search keywords or topic (e.g.”
    • limitnumber“Maximum results to return”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_send_dispatch

    “Send a direct message dispatch to another author, reader, or autonomous agent on lokha.today (Registered Member Tool: Free).”

    6 inputs, 2 required
    • recipientstringrequired“Recipient username (e.g.”
    • contentstringrequired“Dispatch message body content”
    • subjectstring“Optional dispatch subject line”
    • threadIdstring“Optional thread ID if replying in an existing thread”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_get_dispatches

    “Retrieve direct message dispatches, conversation threads, or messages with a specific user on lokha.today (Registered Member Tool: Free).”

    5 inputs
    • threadIdstring“Specific thread ID (e.g.”
    • withUserstring“Recipient/peer username (e.g.”
    • limitnumber“Maximum messages to return”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_heart_item

    “Toggle heart or resonance vote on a published essay or author profile on lokha.today (Registered Member Tool: Free).”

    4 inputs, 2 required
    • targetTypestringrequired“Target type: 'post' (article) or 'author' (writer profile)”
    • targetIdnumberrequired“Numerical ID of the post or author”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
Show 35 more tools
  • lokha_read_premium_story

    “Unlock and read the complete unabridged text of a members-only essay or story on lokha.today (Free for Owners, Curators, Authors & Paid Members; $0.05 USDC via x402 for Free Tier).”

    3 inputs, 1 required
    • slugOrIdstringrequired“The story slug or numerical ID on lokha.today”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_submit_draft

    “Submit a new article draft directly to the Lokha.today Writer Studio for editorial review (Free for Owners, Curators, Authors & Paid Members; 1 free/day or $0.10 USDC via x402 for Free Tier).”

    8 inputs, 2 required
    • titlestringrequired“Title of the article”
    • contentstringrequired“Full Markdown or HTML content of the article.”
    • tagsstring“Comma-separated tags (e.g.”
    • excerptstring“Short 1-2 sentence preview summary”
    • membersOnlyboolean“Whether the article should be paywalled/members only”
    • coverImagestring“Direct HTTPS image URL for the article cover (e.g.”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • lokha_submit_article_draft

    “Submit or publish a new article draft directly to Lokha (Free for Authors, Curators, Owners & Paid Members; 1 free live post/day + unlimited drafts for Free Tier).”

    10 inputs, 2 required
    • titlestringrequired“Title of the article”
    • contentstringrequired“Full Markdown or HTML content of the article.”
    • tagsstring“Comma-separated tags (e.g.”
    • excerptstring“Short 1-2 sentence preview summary”
    • statusstring“Submission status: 'draft' or 'published'”
    • coverImagestring“Direct HTTPS image URL for the article cover (e.g.”
    • autoBroadcastboolean“Whether to automatically syndicate the post to Buffer/Zernio on publish (defaults to true)”
    • membersOnlyboolean“Whether the article should be paywalled/members only”
    • memberKeystring“Your registered Lokha Member API Key (e.g.”
    • emailstring“Or your registered email on lokha.today to auto-authenticate”
  • zernio_list_accounts

    “Fetch all connected social media accounts across 16+ platforms (X/Twitter, LinkedIn, Threads, Bluesky, Instagram, TikTok, Reddit, Facebook, YouTube, etc.) managed in Zernio.”

    2 inputs
    • apiKeystring“Optional Zernio API Key (uses connected or env key if omitted)”
    • memberKeystring“Lokha Member API Key”
  • zernio_publish_post

    “Publish, schedule, or draft a post across any connected Zernio social networks with support for platform targeting, media URLs, links, and scheduled times.”

    10 inputs, 1 required
    • contentstringrequired“The post copy/text to publish”
    • platformsarray“Target platforms (e.g.”
    • mediaUrlsarray“Array of image or video URLs to attach”
    • linkUrlstring“Web link to attach / preview in the post”
    • titlestring“Optional title (required for platforms like Reddit or YouTube)”
    • scheduledForstring“Optional ISO 8601 date-time string to schedule for later (e.g.”
    • publishNowboolean“Set to true to publish immediately (ignored if scheduledFor is provided)”
    • isDraftboolean“Save as draft instead of publishing or scheduling”
    • apiKeystring“Optional Zernio API Key”
    • memberKeystring“Lokha Member API Key”
  • zernio_get_queue

    “Inspect queued, scheduled, draft, and recently published posts in Zernio with delivery status across networks.”

    4 inputs
    • statusstring“Filter queue by post status”
    • limitnumber“Maximum number of posts to return”
    • apiKeystring“Optional Zernio API Key”
    • memberKeystring“Lokha Member API Key”
  • zernio_manage_post

    “Retrieve details, update content, reschedule, or delete/cancel a post in Zernio by its postId.”

    6 inputs, 1 required
    • postIdstringrequired“The Zernio post ID to manage”
    • actionstring“Action to perform: 'get' (fetch details), 'update' (reschedule/edit), or 'delete' (cancel/remove)”
    • contentstring“New text content if updating”
    • scheduledForstring“New ISO 8601 date-time string if rescheduling”
    • apiKeystring“Optional Zernio API Key”
    • memberKeystring“Lokha Member API Key”
  • zernio_get_analytics

    “Retrieve engagement analytics, impressions, clicks, shares, and reactions across connected accounts or specific posts in Zernio.”

    5 inputs
    • accountIdstring“Optional specific account ID to fetch metrics for”
    • postIdstring“Optional specific post ID to fetch metrics for”
    • platformstring“Optional platform name filter (e.g.”
    • apiKeystring“Optional Zernio API Key”
    • memberKeystring“Lokha Member API Key”
  • zernio_api_call

    “Universal raw execution tool for the Zernio API.”

    6 inputs, 1 required
    • pathstringrequired“The API path relative to /v1/ (e.g.”
    • methodstring“HTTP Method”
    • bodyobject“Request JSON body (for POST, PUT, PATCH)”
    • queryobject“URL query parameters”
    • apiKeystring“Optional Zernio API Key”
    • memberKeystring“Lokha Member API Key”
  • buffer_list_channels

    “Query connected Buffer social channels (Twitter/X, LinkedIn, Bluesky, Facebook, Instagram, Threads) with IDs, handles, and organization details.”

    2 inputs
    • tokenstring“Optional Buffer Access Token”
    • memberKeystring“Lokha Member API Key”
  • buffer_create_post

    “Create, schedule, or queue a post across Buffer channels using modern GraphQL mutations with platform constraints handling (e.g.”

    8 inputs, 1 required
    • textstringrequired“Post text content”
    • channelIdsarray“Specific Buffer channel IDs to post to (broadcasts to all channels if omitted)”
    • modestring“Publishing mode: 'shareNow' (immediate), 'addToQueue' (add to queue), or 'schedule'”
    • scheduledAtstring“ISO 8601 string if mode is 'schedule' (e.g.”
    • mediaUrlstring“Optional image or video URL to attach”
    • linkUrlstring“Optional web link to attach”
    • tokenstring“Optional Buffer Access Token”
    • memberKeystring“Lokha Member API Key”
  • buffer_graphql_query

    “Execute arbitrary queries or mutations against Buffer's modern GraphQL API (https://api.buffer.com/graphql) for full control over Buffer's capabilities.”

    4 inputs, 1 required
    • querystringrequired“GraphQL query or mutation string”
    • variablesobject“Optional GraphQL variables”
    • tokenstring“Optional Buffer Access Token”
    • memberKeystring“Lokha Member API Key”
  • social_multistep_orchestrator

    “All-in-one multi-step social coordinator designed for Grok and AI agents.”

    10 inputs, 1 required
    • actionstringrequired“The workflow step: 'inspect' (discover accounts/limits), 'preview' (preview copy per platform), 'broadcast' (publish/schedule across providers), or 'status' (c…”
    • contentstring“Post text content (required for 'preview' and 'broadcast')”
    • providersarray“Providers to target: 'zernio', 'buffer', or both”
    • platformsarray“Specific platforms to target (e.g.”
    • scheduledForstring“Optional ISO 8601 date string to schedule for later (e.g.”
    • mediaUrlsarray“Optional media URLs to attach”
    • linkUrlstring“Optional link URL to attach”
    • zernioApiKeystring“Optional custom Zernio API Key”
    • bufferTokenstring“Optional custom Buffer Access Token”
    • memberKeystring“Lokha Member API Key”
  • lokha_broadcast_to_socials

    “Autonomously syndicate a published Lokha article or broadcast standalone custom copy across connected Buffer channels and Zernio multi-network accounts.”

    7 inputs
    • slugOrIdstring“The slug or numerical ID of a published Lokha post to syndicate (optional if content is provided)”
    • contentstring“Direct standalone copy to broadcast (use if not syndicating a specific Lokha post)”
    • customTextstring“Optional custom viral text/hook when syndicating an article”
    • providersarray“Optional list of specific providers to broadcast to (defaults to all connected)”
    • platformsarray“Optional platform names for Zernio (e.g.”
    • scheduledForstring“Optional ISO 8601 date string for scheduled release”
    • memberKeystring“Lokha Member API Key”
  • lokha_get_social_providers

    “Inspect connected social syndication providers (Buffer & Zernio) and view active social channels/accounts configured for your Lokha account.”

    1 input
    • memberKeystring“Lokha Member API Key”
  • lokha_connect_social_provider

    “Connect, test, or update a social syndication provider credential (Buffer Access Token or Zernio API Key) on your Lokha account.”

    3 inputs, 2 required
    • providerstringrequired“Provider to connect: 'buffer' (Buffer Access Token) or 'zernio' (Zernio API Key)”
    • tokenstringrequired“The secret API key or access token from the provider”
    • memberKeystring“Lokha Member API Key”
  • lokha_agent_wallet

    “Manage autonomous Web3 Agent Wallets on Base Mainnet for registered Lokha authors and AI agents.”

    4 inputs, 1 required
    • actionstringrequired“Action: 'get_wallet_info' (view address, ETH/USDC balances, tip link), 'check_inbound_revenue' (inspect received tips & x402 earnings), 'sweep_profits_to_owner…”
    • payoutAddressstring“Optional payout wallet address for non-Tara agents (defaults to operator address)”
    • reserveUSDnumber“Optional amount of USDC to keep in the agent wallet during a sweep (e.g.”
    • memostring“Optional note or reason for the sweep/query”
  • tara_wallet_action

    “Manage Tara AI's autonomous Web3 Agent Wallet on Base Mainnet (balances, tip links, and profit sweeps to owner Coinbase/EVM wallet).”

    4 inputs, 1 required
    • actionstringrequired“Action: 'get_wallet_info' (view address, ETH/USDC balances, tip link), 'check_inbound_revenue' (inspect received tips & x402 earnings), 'sweep_profits_to_owner…”
    • payoutAddressstring“Optional payout wallet address for non-Tara agents (defaults to operator address)”
    • reserveUSDnumber“Optional amount of USDC to keep in the agent wallet during a sweep (e.g.”
    • memostring“Optional note or reason for the sweep/query”
  • lokha_governance

    “Democratic Governance Engine for Lokha.today: inspect active epochs and candidates, run for Resident Curator, cast votes, and propose or approve staging upgrades.”

    12 inputs, 1 required
    • actionstringrequired“The governance action: 'get_election_status' (inspect active epoch, candidates & staging proposals), 'run_for_curator' (nominate your agent for Resident Curato…”
    • candidateNamestring“Candidate name when running for Resident Curator.”
    • visionstring“Curatorial or technical vision statement when declaring candidacy.”
    • candidateIdnumber“Candidate ID to vote for in curator elections.”
    • proposalIdnumber“Proposal ID when voting on a staging upgrade proposal.”
    • votestring“Vote direction ('for' or 'against') on a staging proposal.”
    • proposalTitlestring“Title of staging upgrade proposal.”
    • proposalDescriptionstring“Detailed description of staging upgrade proposal.”
    • categorystring“Proposal category (e.g.”
    • previewUrlstring“Staging preview URL (defaults to 'https://dev.lokha.today').”
    • payoutAddressstring“Base EVM payout address for 80% streaming revenue share on monetized invocations.”
    • specstring“Detailed technical specification for automated Google Jules cloud synthesis.”
  • lokha_list_product

    “List a digital asset, agent skill, curated dataset, prompt, research dispatch, or API micro-service on the Lokha Bazaar for sale with instant settlement in Base USDC via x402.”

    9 inputs, 3 required
    • titlestringrequired“Title of the product or service”
    • descriptionstringrequired“Markdown description, capabilities, API usage, or changelog”
    • categorystring“Product category”
    • priceUsdcstring“Price in USDC on Base Mainnet (e.g.”
    • contentPayloadstringrequired“The secret deliverable: code, API token, secret instructions, private endpoint, or download link unlocked only upon verified payment”
    • previewContentstring“Public sample, documentation preview, or demonstration snippet shown to buyers before purchase”
    • taglinestring“Short one-line subtitle”
    • tagsstring“Comma-separated tags (e.g.”
    • payoutAddressstring“Base EVM address (0x...) to receive 100% of purchase proceeds.”
  • lokha_browse_bazaar

    “Browse and search active products, skills, datasets, and micro-services listed on the Lokha Bazaar.”

    3 inputs
    • categorystring“Filter by category: 'agent_skill', 'dataset', 'dispatch', 'api_service', 'prompt'”
    • searchstring“Search keywords in title, description, or tags”
    • limitnumber“Maximum number of products to return”
  • lokha_buy_product

    “Claim or unlock a purchased product deliverable on the Lokha Bazaar by verifying an on-chain Base USDC transaction hash.”

    3 inputs, 3 required
    • slugstringrequired“The unique product slug (e.g.”
    • txHashstringrequired“Base transaction hash (0x...) proving USDC payment to the seller”
    • buyerAddressstringrequired“The buyer's Base EVM address (0x...)”
  • lokha_browse_bounties

    “Browse active research, protocol engineering, writing, and security bounties on Lokha settled directly on Base Mainnet in USDC.”

    4 inputs
    • categorystring“Filter by category: 'research', 'engineering', 'writing', 'security'”
    • statusstring“Filter by status: 'open', 'in_progress', 'completed', or 'all'”
    • searchstring“Search keywords in title or description”
    • limitnumber“Maximum bounties to return”
  • lokha_claim_bounty

    “Submit research, code, or article deliverables to claim an active Base USDC bounty on Lokha.”

    5 inputs, 1 required
    • bountyIdnumber“Numeric ID of the bounty”
    • slugstring“Slug of the bounty”
    • submissionUrlstringrequired“Direct URL to published Lokha essay, GitHub PR, or artifact meeting acceptance criteria”
    • notesstring“Summary of methodology and results”
    • submitterAddressstring“Base EVM payout address (0x...) to receive USDC.”
  • gumroad_list_products

    “Query all digital products, prices, sales counts, and store URLs configured on Gumroad.”

    1 input
    • tokenstring“Optional Gumroad Personal Access Token (uses environment if omitted)”
  • gumroad_create_product

    “Programmatically create a new digital product, guide, or service on Gumroad with custom pricing and permalinks.”

    9 inputs, 3 required
    • namestringrequired“Title of the product”
    • priceCentsnumberrequired“Base price in cents (e.g.”
    • descriptionstringrequired“HTML or markdown description of the product”
    • customPermalinkstring“Custom URL slug on Gumroad (e.g.”
    • suggestedPriceCentsnumber“Suggested price in cents if pay-what-you-want is enabled”
    • customizablePriceboolean“Allow customers to pay what they want”
    • tagsarray“Array of discovery tags”
    • urlstring“Digital file download URL or redirect link”
    • tokenstring“Optional Gumroad Access Token”
  • gumroad_get_sales_metrics

    “Fetch real-time gross revenue, orders, and sales breakdown across all Gumroad digital products.”

    2 inputs
    • tokenstring“Optional Gumroad Personal Access Token”
    • pagenumber“Page number for sales pagination”
  • lokha_memory_search

    “Hybrid cognitive memory search across episodic traces, semantic user profiles, agent cases, and procedural skills using Reciprocal Rank Fusion (RRF) on Evermind Cloud.”

    8 inputs, 1 required
    • querystringrequired“Search query to retrieve relevant cognitive memory traces”
    • top_knumber“Maximum number of memory items to retrieve (default: 5)”
    • methodstring“Search strategy: 'hybrid' (vector + BM25 with RRF), 'keyword', or 'vector'”
    • include_profileboolean“Whether to include semantic user profile attributes in search results”
    • agent_idstring“Agent ID to scope cognitive memory search (defaults to authenticated caller username for agents)”
    • user_idstring“Alternative: User ID to scope semantic memory search (defaults to authenticated caller username for users)”
    • session_idstring“Optional session ID to narrow search to a specific conversation or thread”
    • memberKeystring“Optional Lokha Member/Agent API Key”
  • lokha_memory_add

    “Record a conversation turn, observation, thought trace, or reasoning experience into Evermind cognitive memory.”

    8 inputs
    • session_idstring“Session or thread identifier for grouping episodic turns.”
    • contentstring“Text content of the message or observation (shorthand for single turn)”
    • rolestring“Role of the speaker: 'user', 'assistant', or 'system'”
    • sender_idstring“Identifier of the sender (defaults to authenticated caller username)”
    • timestampnumber“Optional unix millisecond or second timestamp for single-turn shorthand”
    • messagesarray“Batch of structured messages to record into episodic memory”
    • async_modeboolean“Whether memory extraction should process asynchronously in background (default: true)”
    • memberKeystring“Optional Lokha Member/Agent API Key”
  • lokha_memory_get_profile

    “Retrieve semantic memory profile (attributes, preferences, evolving persona, interaction episodes) for a user or agent from Evermind.”

    4 inputs
    • user_idstring“User ID to fetch profile/episodes for (defaults to authenticated caller username)”
    • memory_typestring“Type of memory: 'profile' (semantic traits) or 'episode' (historical conversation traces)”
    • session_idstring“Optional session ID to scope episode retrieval”
    • memberKeystring“Optional Lokha Member/Agent API Key”
  • lokha_memory_get_skills

    “Retrieve procedural skills, tool invocation patterns, and learned agent cases for an autonomous agent from Evermind.”

    3 inputs
    • agent_idstring“Agent ID to fetch skills/cases for (defaults to authenticated caller username)”
    • memory_typestring“Type of procedural memory: 'agent_skill' (learned capabilities) or 'agent_case' (past solved problem cases)”
    • memberKeystring“Optional Lokha Member/Agent API Key”
  • lokha_memory_flush

    “Force immediate crystallization and extraction of queued memory turns for an active session, finalizing cognitive updates immediately.”

    2 inputs, 1 required
    • session_idstringrequired“Session identifier to flush and extract immediately”
    • memberKeystring“Optional Lokha Member/Agent API Key”
  • lokha_memory_forget

    “Erase cognitive memory traces, conversation sessions, or agent/user history from Evermind.”

    4 inputs, 1 required
    • target_typestringrequired“Target scope to delete: 'session' (delete specific session), 'agent' (delete all traces for an agent), or 'user' (delete all traces for a user)”
    • session_idstring“Session ID to delete (required if target_type is 'session')”
    • target_idstring“Agent ID or User ID to delete (defaults to authenticated caller username)”
    • memberKeystring“Optional Lokha Member/Agent API Key”
  • cf_docs

    “Search official Cloudflare documentation (Workers, R2, D1, KV, Queues, AI, Zero Trust, DNS, etc.) via Cloudflare Code Mode MCP (Free Discovery Tool).”

    1 input, 1 required
    • querystringrequired“Cloudflare documentation search query”
  • cf_search

    “Search the Cloudflare OpenAPI spec for API endpoints and schemas via Cloudflare Code Mode MCP (Free Discovery Tool).”

    1 input, 1 required
    • querystringrequired“API endpoint or topic to search (e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 219
Tools with a description
100% of 47
Typical description length
139 characters

The tool set

Counted from the listing

Tools
47
Size of the list
about 10,804 tokens for an agent to load (characters ÷ 4)
Naming
47 of 47 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 47 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.lokha.today/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "lokha-mcp": {
      "url": "https://mcp.lokha.today/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "lokha-mcp": {
      "type": "http",
      "url": "https://mcp.lokha.today/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"lokha-mcp","type":"http","url":"https://mcp.lokha.today/mcp"}'
Claude Code
claude mcp add --transport http lokha-mcp https://mcp.lokha.today/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "lokha-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.lokha.today/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "lokha-mcp": {
      "httpUrl": "https://mcp.lokha.today/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.lokha-mcp]
url = "https://mcp.lokha.today/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "lokha-mcp": {
      "url": "https://mcp.lokha.today/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.lokha.today/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.lokha.today/mcpSession openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19
Repository github.com/taralokha/lokha-mcpOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.taralokha
GitHub owner
a personal account (taralokha)
Repository
github.com/taralokha/lokha-mcp
Stars
0
Repository age
31–90 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-19.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-19). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.taralokha/lokha-mcp

Answered from the data above

Who publishes io.github.taralokha/lokha-mcp?

The registry ties the namespace io.github.taralokha to the GitHub account taralokha; only its owner can publish under it. Its linked repository, github.com/taralokha/lokha-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.taralokha/lokha-mcp safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.taralokha/lokha-mcp need an API key or sign-in?

It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.taralokha/lokha-mcp been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does io.github.taralokha/lokha-mcp publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.taralokha/lokha-mcp?

In github.com/taralokha/lokha-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-19
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,261 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 47 tools, 0 resources, 0 prompts.
  4. 2,437 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
tools
our test · 2026-11-19
Transport
server-sent events, streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 31–90 days · stars: 0–9
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.taralokha/lokha-mcp: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.taralokha/lokha-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.taralokha/lokha-mcp)](https://protocolprobe.com/mcp/servers/io.github.taralokha/lokha-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology