NOID Agent Kit
REMOTE · NOID-AGENT-KIT.ONRENDER.COM
Remote MCP for Parano1d (NOID): invoices, receipts, whale/token alerts, launch kit. Credits.
Available components
Last scanned (14 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 17 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 Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 827 tokens (~48/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 16% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 17 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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
- Tool “claim_payment” rewrote its description, which is the text the model reads security
- Schema quality: 42 → 48 ▼ functional
- Tool coverage: 4% → 16% ▲ functional
- New tool “create_topup_intent” functional
- “claim_payment” added an optional parameter “intent_id” cosmetic
- 10 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 59
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://noid-agent-kit.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8d72a13c2c41648513b9d014eb5e0339 |
| SANs: onrender.com, *.onrender.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 noid-agent-kit.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| onrender.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://noid-agent-kit.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://noid-agent-kit.onrender.com/mcp | HTTPS enforced | 301 | https://noid-agent-kit.onrender.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 →
check_invoice ~30
Refresh an invoice against the public permanode API and return confirmation status.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | – |
No output schema declared.
No examples provided.
claim_payment ~77
Credit this API key after sending the exact USDC amount from create_topup_intent to PAYMENT_ADDRESS.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | – | Intent from create_topup_intent. Optional if this key has one matching open intent. |
| tx_hash | string | yes | Base mainnet transaction hash of the USDC Transfer (0x-prefixed). |
No output schema declared.
No examples provided.
create_invoice ~100
Create a checkout invoice. Payer sends NOID to the MERCHANT o1 address. This server never holds funds or secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_micronoid | string | – | – |
| expires_in_seconds | integer | – | – |
| memo | string | – | – |
| merchant_address | string | yes | – |
| quote_id | string | – | – |
| required_confirmations | integer | – | – |
| usd | number | – | – |
| webhook_url | string | – | – |
No output schema declared.
No examples provided.
create_launch_kit ~99
Native NOID asset launch checklist from public protocol docs. Optionally calls Launchkit MCP generate tools when CREATIVE_MCP_* env vars are set. Never submits on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| creator_curve_buy_fraction | number | – | – |
| description | string | – | – |
| name | string | yes | – |
| ticker | string | yes | – |
| tier | string | – | – |
| website | string | – | – |
| whole_token_supply | integer | yes | – |
No output schema declared.
No examples provided.
create_topup_intent ~117
Reserve a unique USDC amount for this API key. Send that exact amount to PAYMENT_ADDRESS, then claim_payment. Receive-only; this server never holds a private key.
| Name | Type | Req | Description |
|---|---|---|---|
| from_address | string | – | Optional paying wallet (0x…). When set, only that sender can match this intent. |
| pack_id | string | – | Credit pack id, e.g. pack_10, pack_25, pack_50, plan_desk. |
| usd | number | – | Custom USDC amount if not using a listed pack. |
No output schema declared.
No examples provided.
get_balance ~17
Return remaining credits, plan, and spend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_hashrate_shift ~20
Network hashrate versus the previous cached sample.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mempool_highlights ~26
Pending mempool size, fee floor, and a short highlight list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_new_tokens ~29
Newest native assets/listings from the public explorer native API.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_payment_info ~35
USDC-on-Base receiving address, packs, and x402 instructions. Receive-only: this server never holds a private key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_quote ~52
Lock a USD→μNOID quote for ~30 minutes. Requires NOID_USD_RATE or PRICE_FEED_URL (not explorer premium).
| Name | Type | Req | Description |
|---|---|---|---|
| micronoid | string | – | – |
| usd | number | – | – |
No output schema declared.
No examples provided.
get_whale_moves ~42
Rich-list balance changes over a μNOID threshold vs the cached snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| threshold_micronoid | string | – | – |
No output schema declared.
No examples provided.
list_invoices ~17
List invoices created by this API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pricing ~41
List credit prices. 1 credit = $0.01. Top up with get_payment_info + claim_payment (USDC on Base) or x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_watchlists ~17
List watchlists for this API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
upsert_watchlist ~59
Create or update a watchlist. Optional https webhook is HMAC-signed on change.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| params | object | – | – |
| watchlist_id | string | – | – |
| webhook_url | string | – | – |
No output schema declared.
No examples provided.
verify_receipt ~49
Verify a pasted Parano1d payment receipt hex or txid against explorer data (and optional local RPC paranoid_verifyReceipt).
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | string | – | – |
| txid | string | – | – |
No output schema declared.
No examples provided.
How do I install the NOID Agent Kit MCP server?
NOID Agent Kit is a hosted endpoint at https://noid-agent-kit.onrender.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 · noid-agent-kit.onrender.com
claude mcp add --transport http com-onrender-noid-agent-kit-noid-agent-kit 'https://noid-agent-kit.onrender.com/mcp'
What is the NOID Agent Kit MCP server?
NOID Agent Kit is an MCP server listed in the public MCP registry as com.onrender.noid-agent-kit/noid-agent-kit. Remote MCP for Parano1d (NOID): invoices, receipts, whale/token alerts, launch kit. Credits. This page covers its hosted endpoint (https://noid-agent-kit.onrender.com/mcp).
Is the NOID Agent Kit MCP server safe to use?
NOID Agent Kit 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 NOID Agent Kit MCP server expose?
NOID Agent Kit exposes 17 tools: list_pricing, get_balance, get_payment_info, create_topup_intent, claim_payment, and 12 more. Their descriptions and schemas cost roughly 827 tokens of context every time the server is loaded.
Does the NOID Agent Kit MCP server require authentication?
No. We connected to NOID Agent Kit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NOID Agent Kit MCP server still maintained?
NOID Agent Kit 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 NOID Agent Kit MCP server?
VerifyMCP ran 12 checks on NOID Agent Kit, 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 NOID Agent Kit: 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.