io.github.rog0x/api
NPM · @ROG0X/MCP-API-TOOLS
HTTP client, JWT decode, header analysis for AI agents
Available components
Last scanned (3 hours ago)
Scores higher than 80% of npm servers
Category Security
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
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 405 tokens (~81/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 5 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 (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.83 → pass security
- 15 Oct 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-api-tools@1.0.2
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 →
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 →
api_health ~51
Check the health of multiple API endpoints. Returns status, response time, SSL certificate validity, and optional response body validation for each endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoints | array | yes | Array of endpoints to check (max 20) |
No output schema declared.
No examples provided.
header_analyzer ~82
Analyze HTTP response headers for security (HSTS, CSP, X-Frame-Options, etc.), caching directives, CORS configuration, cookies, and server information. Provides a security grade.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object | – | HTTP response headers as key-value pairs to analyze |
| url | string | – | Alternatively, provide a URL to fetch and analyze its response headers |
No output schema declared.
No examples provided.
http_request ~151
Make an HTTP request with full control over method, headers, body, authentication, and timeouts. Returns status, headers, body, and timing information.
| Name | Type | Req | Description |
|---|---|---|---|
| auth | object | – | Authentication configuration |
| body | string | – | Request body (for POST, PUT, PATCH) |
| follow_redirects | boolean | – | Whether to follow redirects (default: true) |
| headers | object | – | Key-value pairs of HTTP headers to include |
| method | string | yes | HTTP method: GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS |
| timeout | number | – | Request timeout in milliseconds (default: 30000) |
| url | string | yes | The full URL to send the request to |
No output schema declared.
No examples provided.
jwt_decode ~46
Decode a JWT token without verification. Returns header, payload, expiry, issued-at time, and whether the token is expired.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The JWT token string to decode |
No output schema declared.
No examples provided.
url_parse ~75
Parse a URL into its component parts: protocol, host, port, path, query parameters, hash, and more. Can also build a URL from parts.
| Name | Type | Req | Description |
|---|---|---|---|
| build_params | object | – | Build a URL from parts instead of parsing |
| url | string | – | URL to parse (use this OR build_params, not both) |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/api MCP server?
io.github.rog0x/api runs locally as an npm package, launched with npx -y @rog0x/mcp-api-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-api-tools
claude mcp add rog0x-api -- npx -y @rog0x/mcp-api-tools
What is the io.github.rog0x/api MCP server?
io.github.rog0x/api is an MCP server listed in the public MCP registry as io.github.rog0x/api. HTTP client, JWT decode, header analysis for AI agents. This page covers its npm package (@rog0x/mcp-api-tools).
Is the io.github.rog0x/api MCP server safe to use?
io.github.rog0x/api scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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.rog0x/api MCP server expose?
io.github.rog0x/api exposes 5 tools: http_request, api_health, jwt_decode, url_parse, header_analyzer. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.
Is the io.github.rog0x/api MCP server still maintained?
io.github.rog0x/api is still listed as active in the MCP registry. We last reached this channel on 6 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.rog0x/api MCP server under?
io.github.rog0x/api declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/api MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/api, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.