Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/agentdocs

NPM · @RENETURCIOS/AGENTDOCS · 2 COMPONENTS

Forwarding client for the IMBA agent documentation: facts, use cases, tier policy and doc URLs.

69 Trust /100

Last scanned (4 hours ago)

Scores higher than 37% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 274 tokens (~45/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 5 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 4 Nov 26 69

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/@reneturcios/agentdocs@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~274 tokens

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 →

Tool Tokens
get_agent_facts ~53

Canonical prepaid-agent policy and catalog: Visa prepaid, eSIM, gift cards, KYT address screen, USDT TRC-20, forbidden rails, tiers. Cite as-is. Does not move money.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_agent_use_cases ~53

Playbook: Visa prepaid (flights, datacenter bills), travel eSIM, ~20k gift cards, paid KYT address screen. MCP tools per job. Cite as-is. Does not move money.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_catalog_placement ~27

Which directories take the docs MCP vs the spend MCP. OpenAI is docs-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_public_url ~78

HTTP GET of an allowlisted public docs URL (HowTo, use cases, discovery JSON, llms-agent). Never calls register/deposit/buy.

NameTypeReqDescription
urlstringyesAbsolute https://imbawallet.com URL from the allowlist (HowTo, use cases, tiers, well-known, openapi discovery, llms-agent).

No output schema declared.

No examples provided.

get_tier_policy ~38

Tier 0 vs 1+. Convert closed at 0 (AML). Convert at 1 is a separate request. Withdraw stays closed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_docs_urls ~25

HowTo, use cases, tiers, discovery, OpenAPI, MCP endpoints.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/agentdocs MCP server?

io.github.CloudCorpRecords/agentdocs runs locally as an npm package, launched with npx -y @reneturcios/agentdocs. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/agentdocs

# add to Claude Code
claude mcp add cloudcorprecords-agentdocs -- npx -y @reneturcios/agentdocs
Common questions

What is the io.github.CloudCorpRecords/agentdocs MCP server?

io.github.CloudCorpRecords/agentdocs is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/agentdocs. Forwarding client for the IMBA agent documentation: facts, use cases, tier policy and doc URLs. This page covers its npm package (@reneturcios/agentdocs).

Is the io.github.CloudCorpRecords/agentdocs MCP server safe to use?

io.github.CloudCorpRecords/agentdocs scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/agentdocs MCP server expose?

io.github.CloudCorpRecords/agentdocs exposes 6 tools: get_agent_facts, get_agent_use_cases, get_tier_policy, get_catalog_placement, get_public_url, list_docs_urls. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/agentdocs MCP server still maintained?

io.github.CloudCorpRecords/agentdocs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/agentdocs MCP server under?

io.github.CloudCorpRecords/agentdocs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.