Reclypse Utility Node
REMOTE · A2A.RECLYPSE.AI
Five text and JSON utilities. Paid execution: 0.01 USDC standard or 0.05 USDC priority on Base.
Available components
Last scanned (20 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
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 yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 530. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 26 Oct 26 −38
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 60
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 4 Nov 2026 · Probed https://a2a.reclypse.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reclypse.ai | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6e8417e28f5b33d00ea97c6b7b930a16 |
| SANs: reclypse.ai, *.reclypse.ai | ||||||
| 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 a2a.reclypse.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| reclypse.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 530 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://a2a.reclypse.ai/mcp | HTTP error | 530 | |
| http (plaintext) | http://a2a.reclypse.ai/mcp | HTTPS enforced | 301 | https://a2a.reclypse.ai/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 →
chunk_document Split text into bounded lossless chunks ~89
Prefer paragraph/sentence boundaries, then split deterministically. Concatenated chunks reproduce the input exactly. Limits measure Unicode code points, not model tokens. Retail prices and enabled payment streams are declared in server metadata. Legacy prepaid credits use separate payload quotes.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | Non-whitespace document, at most 64 KiB of UTF-8. |
| max_chunk_size | integer | – | – |
No output schema declared.
No examples provided.
clean_and_chunk Clean and chunk a document ~77
Compound utility: Cleans markdown artifacts and semantically chunks documents in one atomic transaction. Retail prices and enabled payment streams are declared in server metadata. Legacy prepaid credits use separate payload quotes.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | Non-whitespace document, at most 64 KiB of UTF-8. |
| max_chunk_size | integer | – | – |
No output schema declared.
No examples provided.
clean_markdown Extract text and normalize formatting ~64
Extract text from HTML while ignoring script/style content and normalize documented formatting artifacts. Does not promise arbitrary malformed-Markdown repair or HTML security validation. Retail prices and enabled payment streams are declared in server metadata; a valid payment is required for execution.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
No output schema declared.
No examples provided.
sanitize_text Normalize text and flag suspicious instructions ~64
Deterministic Unicode/control-noise normalization and selected instruction-pattern flags. Does not guarantee prompt-injection removal or make untrusted text safe. Retail prices and enabled payment streams are declared in server metadata; a valid payment is required for execution.
| Name | Type | Req | Description |
|---|---|---|---|
| raw_input | string | yes | – |
No output schema declared.
No examples provided.
structure_json Parse strict JSON without inference ~84
Parse JSON or a complete JSON code fence. Default preserves non-JSON text without inventing fields; object requires an object and records requires an array of objects. Rejects duplicate keys/non-finite values. Retail prices and enabled payment streams are declared in server metadata; a valid payment is required for execution.
| Name | Type | Req | Description |
|---|---|---|---|
| schema_target | string | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Reclypse Utility Node MCP server?
Reclypse Utility Node is a hosted endpoint at https://a2a.reclypse.ai/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 · a2a.reclypse.ai
claude mcp add --transport http ai-reclypse-csv-utility-node 'https://a2a.reclypse.ai/mcp'
What is the Reclypse Utility Node MCP server?
Reclypse Utility Node is an MCP server listed in the public MCP registry as ai.reclypse.csv/utility-node. Five text and JSON utilities. Paid execution: 0.01 USDC standard or 0.05 USDC priority on Base. This page covers its hosted endpoint (https://a2a.reclypse.ai/mcp).
Is the Reclypse Utility Node MCP server safe to use?
Reclypse Utility Node scores 23 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 Reclypse Utility Node MCP server expose?
Reclypse Utility Node exposes 5 tools: sanitize_text, structure_json, clean_markdown, chunk_document, clean_and_chunk. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.
Does the Reclypse Utility Node MCP server require authentication?
Its publisher declares no required credentials for Reclypse Utility Node. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Reclypse Utility Node MCP server still maintained?
Reclypse Utility Node is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.