Skip to content

MCP servers › xyz.keyfo › keyfo

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

keyfo MCP server

Registry name xyz.keyfo/keyfo

by keyfo.xyz · domain (the registry's namespace rule)Website ↗

Stock token prices, P&L and trades you sign on Robinhood Chain, plus 300+ AI models on one key. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-12version 1.18.0streamable HTTP24 tools

Summary

xyz.keyfo/keyfo is a remote MCP server listed in the official MCP registry at version 1.18.0, under the namespace of the domain keyfo.xyz. On 2026-11-12 ProtocolProbe connected to it in read-only mode and read its inventory: 24 tools, 4 resources and 12 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: 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: no public GitHub repository

From public records, not a safety rating. Each check with its reason

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

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
24
Last tested
2026-11-12

Tool list size

8,968 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (24 tools). Counted with Anthropic's token counter on 2026-11-12, from the tool list we read on 2026-11-12. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-12 (keyfo.xyz), 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 (1.18.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-12
Mode
read-only (no tool calls)
Latest version
1.18.0, published 2026-11-11 (registry, as of the 2026-11-12 snapshot)
First listed version
2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-12
Package and repository
checked 2026-11-12
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. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. 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-09, listed on 2026-11-12 with version 1.18.0 (published 2026-11-11).

Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12.

What it is

What does this server offer?

Observed inventory
24tools
4resources
12prompts

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

  • “Quote stock tokens and ETFs on Robinhood Chain by ticker (NVDA, TSLA, SPY…) or token address, one or up to 20 at once.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs
    • tickerstring“Ticker of a stock token or ETF, like NVDA.”
    • tickersarray or null“Up to 20 tickers or token addresses to quote at once, like ["NVDA", "CRM"].”
  • stock_movers

    “Today’s movers among stock tokens on Robinhood Chain, ranked by the pool’s 24h change.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs
    • bystring or null“Only change works here: the pool’s 24h change.”
    • topinteger“How many to return, from 1 to 50.”
    • tradeable_onlyboolean“true keeps only stock tokens with a buy route right now (tradeable: true in stock_quote).”
  • stock_portfolio

    “The stock tokens and ETFs a wallet holds on Robinhood Chain, with amounts and value in dollars, plus its ETH.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • walletstringrequired“Wallet address on Robinhood Chain.”
  • “Build unsigned transactions to buy a stock token on Robinhood Chain with ETH (`eth`, or `usd` worth of ETH) or sell `pct` percent of the wallet’s holding for ETH.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 3 required
    • tokenstringrequired“Ticker, like TSLA, or the token address.”
    • sidestringrequired“buy or sell.”
    • walletstringrequired“The wallet that signs and sends.”
    • ethnumber“ETH to spend on a buy, up to 10.”
    • usdnumber“Dollars of ETH to spend, at the current ETH price.”
    • pctnumber“Share of the holding to sell, above 0 and up to 100.”
    • slippage_pctnumber“Price tolerance in percent: 1 by default, from 0.1 to 10.”
  • gift_stock

    “Build an unsigned buy of a stock token on Robinhood Chain that goes to another wallet as a gift: `wallet` pays with its ETH (`usd` worth, or `eth`), and the token arrives at `recipient` in the same t…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 3 required
    • tokenstringrequired“Ticker, like NVDA, or the token address.”
    • walletstringrequired“The wallet that pays and signs.”
    • recipientstringrequired“The wallet that gets the stock token: 0x and 40 hex characters, copied exactly as the user wrote it.”
    • usdnumber“Dollars of ETH to spend, at the current ETH price.”
    • ethnumber“ETH to spend, up to 10.”
    • slippage_pctnumber“Price tolerance in percent: 1 by default, from 0.1 to 10.”
  • “Quote moving funds from another network (ethereum, base, arbitrum, optimism, bnb, polygon and others, 15 in all, or a chain ID) to an agent wallet on Robinhood Chain, arriving as ETH.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 4 required
    • walletstringrequired“Agent wallet on Robinhood Chain that receives the ETH.”
    • payerstringrequired“Wallet that pays on the origin network and signs there.”
    • origin_chainstring or integerrequired“Network to pay from: a name, like base, or its chain ID, like 8453.”
    • amountstring or integerrequired“Amount in the smallest unit of what you pay with, like wei for ETH.”
    • currencystring“Token address to pay with on the origin network.”
  • my_key

    “What your keyfo key can still use: its allowance, what is left and when it resets.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • morpho_rates

    “Morpho on Robinhood Chain: USDG vaults with their net APY, size and curator, and the lending markets that take stock tokens as collateral, with the borrow rate and LLTV.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input
    • tickerstring“Ticker or token address of a stock token, like NVDA.”
  • morpho_loop

    “Work out the net result over a year of borrowing USDG against a stock token on Morpho and putting it in a USDG vault, and the price at which the loan would be liquidated.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 2 required
    • tickerstringrequired“Ticker of the stock token to borrow against, like NVDA.”
    • usdnumberrequired“Dollars of the stock token used as collateral.”
    • borrow_pctnumber“USDG to borrow, as a percent of the collateral value.”
  • build_morpho_deposit

    “Build unsigned transactions to deposit USDG into a Morpho vault on Robinhood Chain, or to withdraw it.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • walletstringrequired“The wallet that signs and sends, and holds the USDG or the vault shares.”
    • sidestring“deposit or withdraw.”
    • usdnumber“USDG to deposit or withdraw (1 USDG is about $1).”
    • pctnumber“Share to move: of the wallet’s USDG for a deposit, of its vault shares for a withdrawal.”
    • vaultstring“Vault address or name from morpho_rates.”
  • “The AI models a keyfo key can call: price per million tokens, context length and what each supports (tools, reasoning, vision, json).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • canstring“What the model must support, comma-separated: tools, reasoning, vision, json.”
    • sortstring“price (cheapest first, the default), context (longest first) or name.”
    • limitinteger“How many to return, from 1 to 100.”
    • querystring“A word in the model ID or name, like gemini or grok.”
  • model_detail

    “One model in detail: prices, context, what it supports, and what a call of a given size would cost.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • modelstringrequired“Model ID with its vendor, like openai/gpt-4.1-mini.”
    • tokens_ininteger“Prompt tokens of a typical call, for the cost estimate.”
    • tokens_outinteger“Answer tokens of a typical call, for the cost estimate.”
Show 12 more tools
  • “Ask another AI model (GPT, Gemini, Grok and others) one question through keyfo and get its answer, for a second opinion.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 1 required
    • promptstringrequired“The question for the other model, with all the context it needs: it does not see this conversation.”
    • modelstring“Model ID with its vendor, like x-ai/grok-4.3 or google/gemini-2.5-flash.”
    • max_tokensinteger“Longest answer in tokens, from 1 to 2048.”
    • systemstring“Optional instructions for the other model.”
  • stock_approvals

    “Open token approvals of a wallet on Robinhood Chain: the stock tokens keyfo lists, USDG and WETH, checked against the spenders keyfo knows, such as LI.FI and Permit2.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • walletstringrequired“Wallet address on Robinhood Chain.”
  • build_revoke

    “Build an unsigned transaction that sets a token approval back to zero, so that spender can no longer move the token.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 3 required
    • walletstringrequired“The wallet that gave the approval.”
    • tokenstringrequired“Ticker (TSLA, USDG, WETH) or token address.”
    • spenderstringrequired“Address the approval was given to, from stock_approvals.”
  • chain_statuson 5 other servers

    “The state of Robinhood Chain: the latest block and its age, the average block time, the gas price, and an estimate of what a transfer and a stock swap cost in dollars.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • “A Robinhood Chain transaction in parts: whether it succeeded, who sent it to what, the function it called, its fee, and every token transfer and approval it made.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • hashstringrequired“Transaction hash on Robinhood Chain, 0x and 64 hex characters.”
  • schedule_buy

    “Plan a weekly buy of a stock token on Robinhood Chain for `wallet`: `usd` or `eth` each week on `weekday` at `hour` in `tz`.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    7 inputs, 4 required
    • tokenstringrequired“Ticker, like NVDA, or the token address.”
    • walletstringrequired“The wallet that buys and signs.”
    • weekdaystringrequired“Day of the week: monday to sunday.”
    • hourintegerrequired“Hour of the day in tz, from 0 to 23.”
    • tzstring“IANA time zone, like Europe/Kyiv or America/New_York.”
    • usdnumber“Dollars of ETH to spend on each buy, at the ETH price at that time.”
    • ethnumber“ETH to spend on each buy.”
  • list_scheduleson 24 other servers

    “The buy plans of `wallet`: token, amount, day, hour and time zone, status and the next time.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • walletstringrequired“Wallet address on Robinhood Chain, 0x…”
  • cancel_scheduleon 5 other servers

    “Cancel a buy plan by its `id`.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    1 input, 1 required
    • idstringrequired“The plan id from schedule_buy or list_schedules.”
  • pending_signs

    “Scheduled buys of `wallet` that are ready to sign now, each with its sign_url and when its window closes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • walletstringrequired“Wallet address on Robinhood Chain, 0x…”
  • buy_at_price

    “Plan a buy of a stock token on Robinhood Chain for `wallet` that waits for a price: when the pool price goes `trigger` below or above `price_usd`, keyfo prepares a buy of `usd` or `eth` and a sign li…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    7 inputs, 4 required
    • tokenstringrequired“Ticker, like NVDA, or the token address.”
    • walletstringrequired“The wallet that buys and signs.”
    • triggerstringrequired“below or above: buy when the pool price drops below or rises above price_usd.”
    • price_usdnumberrequired“The price in dollars that starts the buy, like 160.”
    • usdnumber“Dollars of ETH to spend on the buy, at the ETH price when it is prepared.”
    • ethnumber“ETH to spend on the buy.”
    • repeatboolean“true waits for the price again after each buy.”
  • portfolio_pnlon 1 other server

    “Profit and loss for the stock tokens a wallet holds on Robinhood Chain, read only, no key needed: average entry price, unrealized P&L per token and in total.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • walletstringrequired“Wallet address on Robinhood Chain, 0x…”
    • tickerstring or null“One stock token, like NVDA.”
  • portfolio_brief

    “A short brief for one wallet on Robinhood Chain, read only: each stock token it holds with value and 24h change, the portfolio total, and today’s top three movers you can buy.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • walletstringrequired“Wallet address on Robinhood Chain, 0x…”

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. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. 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-12.

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 69
Tools with a description
100% of 24
Typical description length
371 characters

The tool set

Counted from the listing

Tools
24
Size of the list
about 6,326 tokens for an agent to load (characters ÷ 4)
Naming
24 of 24 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 24 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. 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)

We connected to this URL on 2026-11-12 (a read-only session: no tool was called).

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://keyfo.xyz/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "keyfo": {
      "url": "https://keyfo.xyz/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "keyfo": {
      "type": "http",
      "url": "https://keyfo.xyz/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"keyfo","type":"http","url":"https://keyfo.xyz/mcp"}'
Claude Code
claude mcp add --transport http keyfo https://keyfo.xyz/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "keyfo": {
      "type": "streamableHttp",
      "url": "https://keyfo.xyz/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "keyfo": {
      "httpUrl": "https://keyfo.xyz/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.keyfo]
url = "https://keyfo.xyz/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "keyfo": {
      "url": "https://keyfo.xyz/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://keyfo.xyz/mcp --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • 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-12. 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-12. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.

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 keyfo.xyz/mcpSession openedmatchesour test · 2026-11-12
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-12

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • 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-12. 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 xyz.keyfo/keyfo

Answered from the data above

Who publishes xyz.keyfo/keyfo?

The registry ties the namespace xyz.keyfo to the domain keyfo.xyz; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does xyz.keyfo/keyfo need an API key or sign-in?

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

Has xyz.keyfo/keyfo been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its 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). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

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

Not probed (no operator permission)

We connected and read what the server declares, but did not call its 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). This is our choice, not a block by the server. 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-12
  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: exercised
  13. Fake assistant turns: exercised
  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

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 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 · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 11
  • 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
  • 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 · 3
  • 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-12, 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. 930 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 24 tools, 4 resources, 12 prompts.
  4. 7,571 msFinished: 4 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-12; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-12
MCP capability
prompts, resources, tools
our test · 2026-11-12
Transport
streamable HTTP
registry · 2026-11-12
Required credentials
none declared
registry · 2026-11-12 · 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-12
Lifecycle status
registry · 2026-11-12
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
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-12

“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. “xyz.keyfo/keyfo: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/xyz.keyfo/keyfo

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: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/xyz.keyfo/keyfo)](https://protocolprobe.com/mcp/servers/xyz.keyfo/keyfo)

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