MCP servers › io.github.0xHedgeHood › hedgehood-options
MCP server · registry snapshot 2026-10-29 · last tested 2026-10-29
io.github.0xHedgeHood/hedgehood-options
by 0xHedgeHood · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
Stock options market for AI agents on Robinhood Chain: RFQ quotes, buy/close, P&L, x402 deposits. — the publisher's description
Summary
io.github.0xHedgeHood/hedgehood-options is a remote and local MCP server listed in the official MCP registry at version 0.2.0, under the namespace of the GitHub account 0xHedgeHood. Its linked repository, github.com/0xHedgeHood/hedgehood-agent-kit, belongs to the same GitHub account. On 2026-10-29 ProtocolProbe connected to it in read-only mode and read its inventory: 24 tools, 0 resources and 0 prompts.
Record checks
6 of 8 record checks met · 1 not checked
- 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 checked: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- not met: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: no download figure available
- 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
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- for the package, a secret: HEDGEHOOD_SESSION_KEY_FILE
- Sign-in
- none needed to open a session
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- 2 packages with a critical or high advisory (0 critical, 2 high)
- Repository
- public
- Tools
- 24
- Last tested
- 2026-10-29
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-29 (mcp.hedgehood.io), 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 (0.2.0).
Worth knowing before you connect it
- 2 packages with a critical or high advisory (0 critical, 2 high) in its dependencies (as resolved on 2026-10-29).
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-29
- Mode
- read-only (no tool calls)
- Latest version
- 0.2.0, published 2026-10-28 (registry, as of the 2026-10-29 snapshot)
- First listed version
- 2026-10-28 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-29
- Package and repository
- checked 2026-10-29
- 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; 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-10-28, listed on 2026-10-29 with version 0.2.0 (published 2026-10-28).
Source: the official MCP Registry list on 2026-10-28 and on 2026-10-29.
What it is
What does this server offer?
Observed inventoryNone of its 24 tools are described as changing anything. For 24 the reading was uncertain, so no mark is shown.
- list_marketson 47 other servers
“The option markets: underlying, addresses, version, open expiries.”
Takes no inputs.
- list_instrumentson 5 other servers
“Instruments (expiry x strike x call/put) with their on-chain ids.”
2 inputs
underlyingstring or nullexpirystring or null
- get_mark
“Model bid / ask / mid (USDG per share), delta and whether a quote would be given.”
1 input, 1 required
instrumentstringrequired
- get_quoteon 137 other servers
“A signed quote addressed to `account` for `quantity` shares (buy or sell), valid for seconds, with the exact calldata to send to fillOrderAs from the owner key or the given session key, the fee, the …”
5 inputs, 4 required
instrumentstringrequiredsidestringrequiredquantitystringrequiredaccountstringrequiredsession_keystring or null
- close_quote
“The quote that exits `account`'s open position in `instrument` before expiry: reads the position, takes the opposite side (long -> sell, short -> buy), size = min(|position|, quantity or the whole po…”
4 inputs, 2 required
accountstringrequiredinstrumentstringrequiredquantitystring or nullsession_keystring or null
- get_positionson 22 other servers
“ACTIVE positions: open positions, cost basis and leaderboard row of an account (and its ERC-8004 agent id when it has one).”
1 input, 1 required
accountstringrequired
- get_pnlon 2 other servers
“PnL of an account: every position (open / closed / settled) with the desk's mark, unrealized and realized PnL, fees paid and the total, all USDG raw (1e6) signed from the account's side, plus a one-l…”
1 input, 1 required
accountstringrequired
- get_historyon 42 other servers
“PAST activity of an account, newest first: fills (your side buy / sell, price, premium, fee), settlements (payout, PnL) and redeems, at most `limit` (<= 500) and after `since` (unix seconds), plus a …”
3 inputs, 1 required
accountstringrequiredlimitintegersinceinteger or null
- get_leaderboardon 66 other servers
“Leaderboard per account or per ERC-8004 agent id (by='agent'): fills, premium paid / received, settled PnL.”
3 inputs
bystringorderstringlimitinteger
- get_agent_record
“The ERC-8004 Identity Registry record of an agent id and the accounts seen trading under it.”
1 input, 1 required
agent_idintegerrequired
- how_to_deposit
“How to fund a market balance with USDG over x402 (and the direct deposit path).”
2 inputs
accountstring or nullamountstring or null
- list_vaultson 3 other servers
“The Hedgehood OptionVault v2 funds (hhNVDA-CC, hhNVDA-WHEEL, hhGOOGL-CC, ...): stock token, deposit cap and room, total shares, NAV per share (USDG, from the chain), the current epoch (index, phase, …”
Takes no inputs.
Show 12 more tools
- vault_statuson 3 other servers
“An account's standing in every fund: shares (credited and owed by a frozen deposit), value at NAV, the pending deposit or redemption with its cohort epoch and cutoff, what is claimable, the fund's ep…”
1 input, 1 required
accountstringrequired
- vault_deposit_quote
“The unsigned calldata to deposit `usdg` USDG into `vault` (address or symbol like hhNVDA-CC) for `account`: `txs` = USDG approve (when the allowance is short) then requestDeposit(0, usdg, account), w…”
3 inputs, 3 required
accountstringrequiredvaultstringrequiredusdgstringrequired
- vault_redeem_quote
“The unsigned calldata to redeem `shares` (a decimal or 'all') of `vault` for `account`: requestRedeem(shares, account), the cohort it joins and when it pays, the cancelRedeem calldata.”
3 inputs, 2 required
accountstringrequiredvaultstringrequiredsharesstring
- vault_claim_quote
“The unsigned calldata to collect what `account`'s redemption (or refunded deposit) in `vault` paid: claim(account, account) with the claimable stock and USDG amounts; nothing_to_claim with the pendin…”
2 inputs, 2 required
accountstringrequiredvaultstringrequired
- lend_status
“Share Lending, LEND side: the Morpho Vault V2 that lends USDG against Hedgehood fund shares (hhNVDA-CC) on Morpho Blue — vault, total assets, cap and room, the live market's utilization and borrow ra…”
1 input, 1 required
accountstringrequired
- lend_deposit_quote
“The unsigned calldata to lend `usdg` USDG: `txs` = USDG approve (when the allowance is short) then the vault's ERC-4626 deposit(usdg, account), with the share preview, the APY estimate and the cap / …”
2 inputs, 2 required
accountstringrequiredusdgstringrequired
- lend_withdraw_quote
“The unsigned calldata to take lent USDG back: withdraw(usdg, account, account), or redeem(all shares, account, account) for 'all' (exact, no dust).”
2 inputs, 1 required
accountstringrequiredusdgstring
- borrow_status
“Share Lending, BORROW side: the Morpho Blue market that takes hhNVDA-CC fund shares as collateral for USDG — id (discovered from the lending vault at each call; the mainnet market is being migrated t…”
2 inputs, 1 required
accountstringrequiredmarketstring or null
- borrow_supply_collateral_quote
“The unsigned calldata to post `shares` fund shares (a decimal or 'all' of the wallet) as collateral: approve to Blue (when the allowance is short) + supplyCollateral(marketParams, shares, account, 0x…”
3 inputs, 2 required
accountstringrequiredsharesstringrequiredmarketstring or null
- borrow_take_quote
“The unsigned calldata to borrow `usdg` USDG against posted collateral: borrow(marketParams, usdg, 0, account, account), with the post-action HF / LTV and a `warning` when the resulting LTV is above 7…”
3 inputs, 2 required
accountstringrequiredusdgstringrequiredmarketstring or null
- borrow_repay_quote
“The unsigned calldata to repay USDG debt: approve to Blue (when short) + repay(marketParams, usdg, 0, account, 0x), or for 'all' repay by the exact share debt (no dust; the approval carries 0.1% head…”
3 inputs, 1 required
accountstringrequiredusdgstringmarketstring or null
- borrow_withdraw_collateral_quote
“The unsigned calldata to take fund shares back from Blue: withdrawCollateral(marketParams, shares, account, account), with the post-action HF / LTV and the 70%-of-LLTV warning.”
3 inputs, 1 required
accountstringrequiredsharesstringmarketstring or null
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-10-29.
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
- 0% of 51
- Tools with a description
- 100% of 24
- Typical description length
- 367 characters
The tool set
Counted from the listing
- Tools
- 24
- Size of the list
- about 3,966 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 npm package @hedgehood-io/mcp
This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"hedgehood-options": {
"command": "npx",
"args": [
"-y",
"@hedgehood-io/mcp@0.2.0"
],
"env": {
"HEDGEHOOD_SESSION_KEY_FILE": "<HEDGEHOOD_SESSION_KEY_FILE>"
}
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"hedgehood-options": {
"command": "npx",
"args": [
"-y",
"@hedgehood-io/mcp@0.2.0"
],
"env": {
"HEDGEHOOD_SESSION_KEY_FILE": "<HEDGEHOOD_SESSION_KEY_FILE>"
}
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"hedgehood-options": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hedgehood-io/mcp@0.2.0"
],
"env": {
"HEDGEHOOD_SESSION_KEY_FILE": "${input:hedgehood-session-key-file}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "hedgehood-session-key-file",
"description": "HEDGEHOOD_SESSION_KEY_FILE",
"password": true
}
]
}Claude Code
claude mcp add --env "HEDGEHOOD_SESSION_KEY_FILE=<HEDGEHOOD_SESSION_KEY_FILE>" --transport stdio hedgehood-options -- npx -y @hedgehood-io/mcp@0.2.0
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"hedgehood-options": {
"command": "npx",
"args": [
"-y",
"@hedgehood-io/mcp@0.2.0"
],
"env": {
"HEDGEHOOD_SESSION_KEY_FILE": "<HEDGEHOOD_SESSION_KEY_FILE>"
},
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"hedgehood-options": {
"command": "npx",
"args": [
"-y",
"@hedgehood-io/mcp@0.2.0"
],
"env": {
"HEDGEHOOD_SESSION_KEY_FILE": "<HEDGEHOOD_SESSION_KEY_FILE>"
}
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.hedgehood-options] command = "npx" args = ["-y", "@hedgehood-io/mcp@0.2.0"] [mcp_servers.hedgehood-options.env] "HEDGEHOOD_SESSION_KEY_FILE" = "<HEDGEHOOD_SESSION_KEY_FILE>"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"hedgehood-options": {
"command": "npx",
"args": [
"-y",
"@hedgehood-io/mcp@0.2.0"
],
"env": {
"HEDGEHOOD_SESSION_KEY_FILE": "<HEDGEHOOD_SESSION_KEY_FILE>"
}
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -e "HEDGEHOOD_SESSION_KEY_FILE=<HEDGEHOOD_SESSION_KEY_FILE>" -- npx -y @hedgehood-io/mcp@0.2.0
- Replace <HEDGEHOOD_SESSION_KEY_FILE> with your own values; the entry marks HEDGEHOOD_SESSION_KEY_FILE as secret, so keep the file out of version control.
- Optional settings the entry also lists (left out above): HEDGEHOOD_CHAIN_ID, HEDGEHOOD_ACCOUNT, HEDGEHOOD_OWNER_KEY_FILE, HEDGEHOOD_RPC_URL, HEDGEHOOD_RFQ_URL, HEDGEHOOD_INDEXER_URL, HEDGEHOOD_GATEWAY_URL, HEDGEHOOD_DRY_RUN, HEDGEHOOD_MAX_DEPOSIT.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-29 (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://mcp.hedgehood.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"hedgehood-options": {
"url": "https://mcp.hedgehood.io/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"hedgehood-options": {
"type": "http",
"url": "https://mcp.hedgehood.io/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"hedgehood-options","type":"http","url":"https://mcp.hedgehood.io/mcp"}'Claude Code
claude mcp add --transport http hedgehood-options https://mcp.hedgehood.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"hedgehood-options": {
"type": "streamableHttp",
"url": "https://mcp.hedgehood.io/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"hedgehood-options": {
"httpUrl": "https://mcp.hedgehood.io/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.hedgehood-options] url = "https://mcp.hedgehood.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"hedgehood-options": {
"url": "https://mcp.hedgehood.io/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.hedgehood.io/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.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.2.0
- Latest stable
- 0.2.0
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-10-29. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-29 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-sJqzDtg3pI6rz6Hao…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-10-29.
Does the registry listing match what we found?
Feature #6The 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 says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.hedgehood.io/mcp | Session opened | matches | our test · 2026-10-29 |
| A secret is declared as required | Opened a session without any credential | differs | our test · 2026-10-29 |
| Version 0.2.0 on npm | Exists and can be installed | matches | npm · 2026-10-29 |
| Repository github.com/0xHedgeHood/hedgehood-agent-kit | Opens publicly | matches | api.github.com · 2026-10-29 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.0xHedgeHood
- GitHub owner
- an organization (0xHedgeHood)
- Build record
- signed
- Repository
- github.com/0xHedgeHood/hedgehood-agent-kit
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
Source: the registry entry and api.github.com · 2026-10-29.
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 rating6 of 8 record checks met · 1 not checked
- Not ranked by downloads: no download figure available
- 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 checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- Not metNo known critical or high advisory in the package or its dependencies2 packages in its dependencies with a critical or high advisory (npm audit counts packages, not advisories).What changes this check: npm's documentation describes listing a project's dependency advisories with npm audit and applying compatible dependency updates. npm: npm audit
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-29. 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. How each check works · Leaderboards
Common questions about io.github.0xHedgeHood/hedgehood-options
Answered from the data aboveWho publishes io.github.0xHedgeHood/hedgehood-options?
The registry ties the namespace io.github.0xHedgeHood to the GitHub account 0xHedgeHood; only its owner can publish under it. Its linked repository, github.com/0xHedgeHood/hedgehood-agent-kit, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.0xHedgeHood/hedgehood-options safe to install?
We do not rate servers as safe or unsafe. 6 of its 8 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. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has packages with advisories (2 high; npm audit). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.0xHedgeHood/hedgehood-options need an API key or sign-in?
It opened a session without any credential on 2026-10-29. The registry entry declares a required secret.
Has io.github.0xHedgeHood/hedgehood-options been security tested?
Partly. 2 of the 14 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. This is our choice, not a block by the server. No security verdict is published before verification.
Is the listed version current?
Yes. The registry lists 0.2.0, the latest stable release on npm.
Where is the source code of io.github.0xHedgeHood/hedgehood-options?
In github.com/0xHedgeHood/hedgehood-agent-kit, which opens publicly.
Found this page useful?
Anonymous · no sign-inA 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 (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. 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.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- 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.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants 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
ssrfChecks 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; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks 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; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends 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; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks 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-dataChecks 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-boundaryChecks 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; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks 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-hidingChecks 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-redirectChecks 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-deputyChecks 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
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks 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-validationChecks 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-schemeChecks 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-10-29, 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.
- 0 msStarted a read-only session with the server's remote endpoint
- 902 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 24 tools, 0 resources, 0 prompts.
- 3,311 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.
“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.0xHedgeHood/hedgehood-options: MCP server record.” Data checked 2026-10-29. https://protocolprobe.com/mcp/servers/io.github.0xHedgeHood/hedgehood-options
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
[](https://protocolprobe.com/mcp/servers/io.github.0xHedgeHood/hedgehood-options)
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.
Write to hello@protocolprobe.com · corrections log · methodology