Siro
REMOTE · SIROAGENT.COM
Pay-per-call AI tools for agents over x402: LLMs, image, video, music, market data. USDC/USDG.
Available components
Last scanned (14 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 847 tokens (~169/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- Tool “siro_call” changed its title: Run a paid resource (x402) → Run a paid tool (x402) cosmetic
- Tool “siro_resource_schema” changed its title: Get one resource's input schema → Get one tool's input schema cosmetic
- 14 Nov 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://siroagent.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=siroagent.com | CN=WE1,O=Google Trust Services,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | ab2273a82d58c919135ab05ebe949c93 |
| SANs: siroagent.com, www.siroagent.com, *.www.siroagent.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of siroagent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| siroagent.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://siroagent.com/mcp | Verified | 200 | |
| http (plaintext) | http://siroagent.com/mcp | HTTPS enforced | 301 | https://siroagent.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
siro_call Run a paid tool (x402) ~197
Runs one Siro resource and pays its exact USD price over x402, in USDG on Robinhood Chain or USDC on Solana, Base, Arbitrum or Polygon. Send a signed x402 v2 PaymentPayload in params._meta["x402/payment"]; without it the tool returns isError with the payment requirements (price, networks, payTo) to sign. The work runs before the payment settles, so failed calls are never charged; a successful call returns the result plus a receipt with the transaction hash in _meta["x402/payment-response"]. Agents without an x402 wallet can use the Siro CLI (`siro mcp`), which pays automatically within spending caps.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | Input object matching the resource's schema from siro_resource_schema, e.g. {"network":"base"}. |
| resource | string | yes | Resource id from siro_resources, e.g. "gas-now". |
No output schema declared.
No examples provided.
siro_discover Find third-party x402 services ~160
Searches the open x402 Bazaar index (run by Coinbase CDP) for paid APIs outside Siro's own catalog, such as weather, web search, data enrichment or token prices. Returns each service's URL, HTTP method, price, accepted networks, an example input and whether Siro can pay it (payable = accepts USDG on Robinhood Chain or USDC on Solana, Base, Arbitrum or Polygon). Use it when no Siro resource fits the task. Free, no payment needed.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many services to return (default 10, max 20). |
| query | string | yes | What you need in a few words, e.g. "weather forecast" or "web search". |
No output schema declared.
No examples provided.
siro_resource_schema Get one tool's input schema ~105
Returns everything needed to call one Siro resource: its USD price, the JSON Schema of its input, a ready-to-use example input, what it returns, and its HTTP endpoint. Use it after siro_resources and before siro_call so the input is valid (invalid input is rejected before any payment). Free, no payment needed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Resource id from siro_resources, e.g. "stock-signal" or "prediction-markets". |
No output schema declared.
No examples provided.
siro_resources Search the Siro catalog ~167
Lists Siro's pay-per-call resources (67 in total) with id, name, category, USD price and a one-line summary. Use it first to find the right resource id; then read its input schema with siro_resource_schema and run it with siro_call. Categories: LLMs, image generation, audio (speech and transcription), vision, web (reading and translation), on-chain data on Robinhood Chain and Base, tokenized stocks, Polymarket prediction markets and content tools. Free, no payment needed.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. |
| query | string | – | Optional words to match against the id, name, summary and tags, e.g. "stock", "image", "polymarket". Omit to list everything. |
No output schema declared.
No examples provided.
siro_tokens List swappable tokens ~128
Lists the tokens a Siro wallet can swap through the KyberSwap aggregator on one network, with symbol, name and contract address. On Robinhood Chain this includes ETH, WETH, USDG and every Robinhood stock token (TSLA, NVDA, AAPL…); on Base it includes ETH, WETH and USDC. Use it to resolve a ticker to its contract address before quoting or executing a swap with the Siro CLI. Read-only and free; it does not trade.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Which chain's tokens to list. Defaults to robinhood. |
No output schema declared.
No examples provided.
How do I install the Siro MCP server?
Siro is a hosted endpoint at https://siroagent.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · siroagent.com
claude mcp add --transport http com-siroagent-siro 'https://siroagent.com/mcp'
What is the Siro MCP server?
Siro is an MCP server listed in the public MCP registry as com.siroagent/siro. Pay-per-call AI tools for agents over x402: LLMs, image, video, music, market data. USDC/USDG. This page covers its hosted endpoint (https://siroagent.com/mcp).
Is the Siro MCP server safe to use?
Siro scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Siro MCP server expose?
Siro exposes 5 tools: siro_resources, siro_resource_schema, siro_call, siro_discover, siro_tokens. Their descriptions and schemas cost roughly 757 tokens of context every time the server is loaded.
Does the Siro MCP server require authentication?
No. We connected to Siro without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Siro MCP server still maintained?
Siro is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Siro MCP server?
VerifyMCP ran 12 checks on Siro, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Siro: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.