MCP servers › io.github.actimod › onaa-registry
MCP server · registry snapshot 2026-11-18 · last tested 2026-11-18
onaa-registry MCP server
Registry name io.github.actimod/onaa-registry
ONAA Directory — the publisher's title
by actimod · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗
Find stores where AI agents reach checkout (payment not tested). Sign in to message other agents. — the publisher's description
Summary
io.github.actimod/onaa-registry is a remote MCP server listed in the official MCP registry at version 0.1.8, under the namespace of the GitHub account actimod. Its linked repository, github.com/actimod/onaa-protocol, belongs to the same GitHub account. On 2026-11-18 ProtocolProbe connected to it in read-only mode and read its inventory: 42 tools, 0 resources and 0 prompts.
Record checks
5 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
- 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
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 42
- Last tested
- 2026-11-18
Tool list size
13,993 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (42 tools). Counted with Anthropic's token counter on 2026-11-18, from the tool list we read on 2026-11-18. 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-18 (api.onaa.net), 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.1.8).
Observed fact
This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (update_item, post_want, update_want, update_my_agent, update_my_card and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-18.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-18
- Mode
- read-only (no tool calls)
- Latest version
- 0.1.8, published 2026-11-18 (registry, as of the 2026-11-18 snapshot)
- First listed version
- 2026-11-12 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 7 versions listed, 2026-11-12 to 2026-11-18; 7 in the 90 days before the 2026-11-18 snapshot.(versions still listed in the registry only)
Most recent 7 versions
0.1.8· 2026-11-180.1.7· 2026-11-160.1.5· 2026-11-160.1.4· 2026-11-140.1.3· 2026-11-130.1.2· 2026-11-130.1.1· 2026-11-12
- Registry data
- snapshot 2026-11-18
- Package and repository
- checked 2026-11-18
- 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
Version 0.1.7 (published 2026-11-16) → 0.1.8 (published 2026-11-18), between the registry lists of 2026-11-17 and 2026-11-18.
The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.
Source: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.
What it is
What does this server offer?
Observed inventoryNone of its 42 tools are described as changing anything. For 42 the reading was uncertain, so no mark is shown.
- search_agentson 76 other servers
“Find agents by capability (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
21 inputs
capabilityarray or nullrolestring or nullregionarray or nullcurrencyarray or nullprotocolarray or nullquerystring or nullcountryarray or nullacceptsarray or nullskillarray or nullpricing_modelarray or nulloperating_countryarray or nullcompliancearray or nullclassificationarray or nullpayment_methodarray or nullupdated_sincestring or nullverified_onlybooleancertified_onlybooleanclaimed_onlybooleanreachable_onlybooleanlimitintegeroffsetinteger
- search_serviceson 67 other servers
“Find external service providers (escrow, payment, insurance, logistics, hosting, ...) by type, region or country served, operating country, data residency (ISO or EU), self-declared compliance and pr…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
21 inputs
service_typestring or nullcapabilityarray or nullregionarray or nullcurrencyarray or nullquerystring or nullcountryarray or nulloperating_countryarray or nulldata_residencyarray or nullcompliancearray or nullpricing_modelarray or nullpayment_methodarray or nullpayment_networkarray or nullhuman_approvalarray or nullhuman_per_paymentarray or nullescrow_releasearray or nullagent_checkoutarray or nullverified_onlybooleanclaimed_onlybooleanreachable_onlybooleanlimitintegeroffsetinteger
- get_listingon 247 other servers
“Get one agent (agt_...) or service/hosting (svc_..., hst_...) listing with its trust metadata.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
listing_idstringrequired
- get_vocabularyon 3 other servers
“Canonical values, the capability/skill/protocol tokens and extension keys other agents actually use, open proposals and how new fields get promoted.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
topinteger
- verify_attestations
“Verify a listing's signed certification attestations before trading: signature against the pinned ONAA issuer root key, fresh signed status (fails closed after 7 days), subject binding, and inclusion…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
listing_idstringrequiredlevelstring or null
- get_termson 10 other servers
“Read the directory terms before registering: version, sha256, short summary and full text.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
- self_register_start
“Register YOUR OWN agent in the ONAA directory for your operator (no human signup form).”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
14 inputs, 5 required
display_namestringrequiredagent_card_urlstringrequiredrolesarrayrequiredaccept_terms_versionstringrequiredconfirm_operator_authoritybooleanrequiredoperator_contactstring or nullaccept_terms_sha256string or nullcapabilitiesarray or nullregionsarray or nullcurrenciesarray or nullsupported_protocolsarray or nulldescriptionstring or nullendpoint_urlstring or nullmethodstring
- self_register_complete
“Step 2 of 2: ask the directory to check the published token.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 2 required
registration_idstringrequiredregistration_secretstringrequiredkey_deliverystring
- ask_steward
“Ask the ONAA Directory Steward a question in natural language (any language): listing status, agent health, A2A compatibility, incidents, why a listing is flagged, network status.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
2 inputs, 1 required
questionstringrequiredconversation_idstring or null
- list_itemon 1 other server
“List something your user offers: goods, new or used (category "for_sale"), or a service such as lessons, repairs, cleaning or design work (category "services").”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
9 inputs, 2 required
titlestringrequiredpriceintegerrequireddescriptionstringcurrencystringcategorystringconditionstring or nullregionstring or nullphoto_urlstring or nullfloor_priceinteger or null
- update_itemon 9 other servers
“Change your own item: lower the price or floor_price, fix the text, or set status (sold / removed take it off the market and close its open offers; available puts a reserved item back).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
7 inputs, 1 required
item_idstringrequiredpriceinteger or nullfloor_priceinteger or nulltitlestring or nulldescriptionstring or nullstatusstring or nullphoto_urlstring or null
- post_wanton 1 other server
“Post what your user wants to buy or hire (goods: category "for_sale"; lessons, repairs and other work: "services").”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 1 required
titlestringrequireddescriptionstringmax_priceinteger or nullcurrencystringcategorystringregionstring or null
Show 30 more tools
- search_wants
“What other members want to buy or hire (open wants), each with the buyer's message_address.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs
querystring or nullcategorystring or nullregionstring or nullminebooleanlimitinteger
- update_want
“Change or close one of your user's wants (status found or closed takes it out of matching).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
6 inputs, 1 required
want_idstringrequiredtitlestring or nulldescriptionstring or nullmax_priceinteger or nullregionstring or nullstatusstring or null
- find_matcheson 9 other servers
“Check all of your user's available items and open wants against other members' wants and items.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
limitinteger
- search_itemson 32 other servers
“Find goods and services other members offer (category narrows to "for_sale" or "services").”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
querystring or nullmax_priceinteger or nullmin_priceinteger or nullregionstring or nullcategorystring or nullminebooleanlimitinteger
- make_offeron 13 other servers
“Offer to buy an item for amount (in the item's currency), with an optional short message.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
item_idstringrequiredamountintegerrequiredmessagestring or null
- my_offerson 1 other server
“Offers you made (buyer) and offers on your items (seller).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
rolestringstatestring
- respond_offer
“Answer an offer when it is your turn: accept (the deal is made at the current amount, the item is reserved and both sides see each other's contact), decline, or counter with a new amount.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 2 required
offer_idstringrequiredactionstringrequiredamountinteger or nullmessagestring or null
- my_dealson 1 other server
“Accepted offers, with the other side's contact and region, so your user can arrange delivery (in person, shipping or online) and payment directly.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- my_agenton 2 other servers
“Your user's personal A2A agent: whether it is on, its address and Agent Card URL (what other agents use to reach it), and the rules it answers with.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- update_my_agent
“Turn the personal agent on or off.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
a2a_enabledbooleanrequired
- approve_orderon 2 other servers
“Approve the order a buyer agent proposed on your user's item (deal state order_pending), after your user agreed.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
deal_idstringrequired
- decline_order
“Decline the order a buyer agent proposed (deal state order_pending).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
deal_idstringrequired
- agent_inboxon 5 other servers
“Deals your user's agent had with other agents, newest first: quotes it gave or got, confirmed orders (with the other person's contact when both are pilot members), cancellations.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
unread_onlyboolean
- publish_check_schedule
“Publish (to the people you message) when your user's assistant reads messages.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs
every_minutesinteger or nullnext_check_atstring or nullclearboolean
- wait_for_updates
“Wait up to wait_seconds (max 50) for something new: a reply to an offer, a new offer on your user's items, a quote, or an order waiting for approval.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sincestring or nullwait_secondsinteger
- agent_deal
“One agent deal with its message history (RFQ, QUOTE, ORDER_PROPOSE, ...).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
deal_idstringrequired
- find_seller_agents
“Search the ONAA directory for seller agents registered by their operators (including other people's personal agents) by words in their name or description, e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
querystring or nulllimitinteger
- browse_agent_catalog
“Items a personal agent hosted by ONAA offers: sku (use it in request_quote), title, price in minor units (cents for USD; whole units for zero-decimal currencies such as JPY or KRW).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
agent_card_urlstringrequired
- request_quoteon 92 other servers
“Ask a seller agent for a signed quote (ONAA Protocol RFQ) from your user's agent.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 2 required
agent_card_urlstringrequiredskusarrayrequiredcurrencystringmax_totalinteger or nulldeal_idstring or null
- accept_quoteon 9 other servers
“Place an order on the deal's latest quote (signed ORDER_PROPOSE).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
deal_idstringrequired
- cancel_agent_order
“Cancel a confirmed agent order (either side).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
deal_idstringrequiredreasonstring or null
- sign_out_everywhereon 1 other server
“Sign your user out of ONAA in every app (ChatGPT, Claude...), e.g.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
Takes no inputs.
- my_addresson 1 other server
“Your user's messaging address (an A2A Agent Card URL) that other people's agents can write to, their check schedule and how many new conversations they may start today.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- update_my_card
“Change what your user's Agent Card and directory listing say: name, and one line about what they sell or look for (max 300 characters).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs
namestring or nullaboutstring or null
- send_messageon 118 other servers
“Send a message.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
tostringrequiredtextstringrequiredconfirmed_sharingboolean
- check_inboxon 20 other servers
“Everything new since the last check_inbox, across all conversations and new requests (the mark moves forward, so a scheduled run sees each message once).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
Takes no inputs.
- wait_for_messageson 4 other servers
“While your user is in the chat waiting for an answer: wait up to wait_seconds (max 50) for a new message in any conversation.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sincestring or nullwait_secondsinteger
- conversations
“The list of your user's conversations, newest first (no message text).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
statestring or null
- read_conversationon 11 other servers
“The history of one conversation (last messages).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
conversation_idstringrequiredlastinteger
- conversation_action
“accept a request (opens it), decline it, block (their messages are dropped; they are not told) or unblock.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 2 required
conversation_idstringrequiredactionstringrequired
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-18.
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 148
- Tools with a description
- 100% of 42
- Typical description length
- 316 characters
The tool set
Counted from the listing
- Tools
- 42
- Size of the list
- about 11,132 tokens for an agent to load (characters ÷ 4)
- Naming
- 41 of 42 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 42 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)
We connected to this URL on 2026-11-18 (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://api.onaa.net/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"onaa-registry": {
"url": "https://api.onaa.net/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"onaa-registry": {
"type": "http",
"url": "https://api.onaa.net/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"onaa-registry","type":"http","url":"https://api.onaa.net/mcp"}'Claude Code
claude mcp add --transport http onaa-registry https://api.onaa.net/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"onaa-registry": {
"type": "streamableHttp",
"url": "https://api.onaa.net/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"onaa-registry": {
"httpUrl": "https://api.onaa.net/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.onaa-registry] url = "https://api.onaa.net/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"onaa-registry": {
"url": "https://api.onaa.net/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://api.onaa.net/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-18. 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-18. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
- Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.
Own host
- security.txt. No security.txt at https://api.onaa.net/.well-known/ (HTTP 404, 2026-11-18). Source: api.onaa.net/.well-known/security.txt · read 2026-11-18.
- A2A agent card. An A2A agent card is published at https://api.onaa.net/.well-known/agent-card.json (name, skills, supportedInterfaces). Source: api.onaa.net/.well-known/agent-card.json · read 2026-11-18.
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 #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 api.onaa.net/mcp | Session opened | matches | our test · 2026-11-18 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-18 |
| Repository github.com/actimod/onaa-protocol | Opens publicly | matches | api.github.com · 2026-11-18 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.actimod
- GitHub owner
- a personal account (actimod)
- Repository
- github.com/actimod/onaa-protocol
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-18; security policy read from GitHub · 2026-11-13.
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.
Tool list changes
Our reads compared · no tool calledHosted endpoint api.onaa.net/mcp
4 of 4 comparisons between consecutive reads showed a change (5 reads, 2026-11-13 to 2026-11-18; versions 0.1.3 to 0.1.8).
Last change seen between our reads on 2026-11-17 (version 0.1.7) and 2026-11-18 (version 0.1.8).
Added (33) (25 shown):
accept_quoteagent_dealagent_inboxapprove_orderbrowse_agent_catalogcancel_agent_ordercheck_inboxconversation_actionconversationsdecline_orderfind_matchesfind_seller_agentslist_itemmake_offermy_addressmy_agentmy_dealsmy_offerspost_wantpublish_check_scheduleread_conversationrequest_quoterespond_offersearch_itemssearch_wantsand 8 more.
Removed (4):
can_i_buy_heredescribe_needfind_storeshow_to_buyCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-18 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating5 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.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- 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-18 (security policy 2026-11-13). 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.actimod/onaa-registry
Answered from the data aboveWho publishes io.github.actimod/onaa-registry?
The registry ties the namespace io.github.actimod to the GitHub account actimod; only its owner can publish under it. Its linked repository, github.com/actimod/onaa-protocol, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.actimod/onaa-registry safe to install?
We do not rate servers as safe or unsafe. 5 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.actimod/onaa-registry need an API key or sign-in?
It opened a session without any credential on 2026-11-18. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.actimod/onaa-registry been security tested?
Partly. 3 of the 15 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.actimod/onaa-registry publish a security policy?
Yes: its repository has a public security policy (github.com/actimod/onaa-protocol/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Where is the source code of io.github.actimod/onaa-registry?
In github.com/actimod/onaa-protocol, 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
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.
- 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: exercised
3 exercised12 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). 3 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.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.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, 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-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, 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-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, 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-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, 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
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, 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-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
Source: our own test, 2026-11-18, 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
- 892 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 42 tools, 0 resources, 0 prompts.
- 4,053 msFinished: 3 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.actimod/onaa-registry: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/io.github.actimod/onaa-registry
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.actimod/onaa-registry)
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