io.github.mbeato/apimesh
NPM · @MBEATO/APIMESH-MCP-SERVER · SCANNED AUG 3
74 paid web-analysis APIs (SEO, security, TLS, DNS, email) as MCP tools. USDC via x402.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 99 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 4471 tokens (~58/item across 76 items; 76 tools + 0 resources), lean.Pass
- 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mbeato/apimesh-mcp-server
claude mcp add mbeato-apimesh -- npx -y @mbeato/apimesh-mcp-server
codex mcp add mbeato-apimesh -- npx -y @mbeato/apimesh-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mbeato-apimesh": {
"type": "local",
"command": [
"npx",
"-y",
"@mbeato/apimesh-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add mbeato-apimesh --command npx --arg -y --arg @mbeato/apimesh-mcp-server
mcp_servers:
mbeato-apimesh:
command: "npx"
args: ["-y", "@mbeato/apimesh-mcp-server"] {
"mcpServers": {
"mbeato-apimesh": {
"command": "npx",
"args": [
"-y",
"@mbeato/apimesh-mcp-server"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +22
- Install scripts: pass → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- License: pass → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 1 Aug 26 −17
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +31
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → fair ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: MIT functional
- 29 Jul 26 −20
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 40
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 3 Aug 2026 · Analysed npm/@mbeato/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
ssl_tls_inception_score ~52
Comprehensive SSL/TLS certificate and protocol audit for the specified hostname or URL
| Name | Type | Req | Description |
|---|---|---|---|
| hostname | string | yes | Hostname or URL (http(s):// or plain hostname) to analyze SSL/TLS for |
No output schema declared.
No examples provided.
ssl_tls_risk_analyzer ~56
Aggregates SSL/TLS configuration details from public scans, DNS records, and certificate transparency logs, then performs a risk assessment
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | Hostname or URL to analyze (http(s):// optional) |
No output schema declared.
No examples provided.
ssl_tls_threat_assessment ~39
Comprehensive TLS security threat assessment for a domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain or hostname to assess SSL/TLS configurations for |
No output schema declared.
No examples provided.
status_code_checker ~63
Check the live HTTP status code of any URL. Returns the actual status code, reason phrase, and response headers. Simpler than http_status_checker — no expected-code validation.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to check (must include http:// or https://) |
No output schema declared.
No examples provided.
subdomain_exposure_heatmap ~50
Exhaustive subdomain enumeration from multiple sources, risk analysis, exposure scoring, recommendations and heatmap report
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain to audit (e.g. example.com) |
No output schema declared.
No examples provided.
subdomain_exposure_ranking ~62
Comprehensive paid scan: exhaustive subdomain enumeration from DNS, CT logs, plus HTTP endpoint probing, header analysis, TLS version checks, outdated service detection, with full scoring and rich recommendations
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain to enumerate and analyze |
No output schema declared.
No examples provided.
subdomain_exposure_rankings ~37
Paid, comprehensive analysis of subdomain exposure and security ranking
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Root domain to enumerate and analyze |
No output schema declared.
No examples provided.
subdomain_exposure_score ~36
Paid comprehensive full subdomain exposure scoring and audit report
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze subdomains for |
No output schema declared.
No examples provided.
subdomain_exposure_scorer ~42
Comprehensive enumeration and exposure scoring of all detected subdomains for a domain
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Base domain, e.g. example.com |
No output schema declared.
No examples provided.
subdomain_risk_ranking ~46
Perform a deep, comprehensive subdomain enumeration and risk ranking audit
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The root domain to enumerate subdomains for (e.g. example.com) |
No output schema declared.
No examples provided.
subdomain_vulnerability_ranker ~42
Exhaustive subdomain enumeration, vulnerability inference, scoring, and recommendations
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Target root domain (e.g. example.com) |
No output schema declared.
No examples provided.
subdomain_vulnerability_ranking ~36
Paid comprehensive subdomain enumeration and vulnerability ranking
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to enumerate e.g. example.com |
No output schema declared.
No examples provided.
subdomain_vulnerability_rankings ~38
Paid comprehensive subdomain enumeration and vulnerability ranking
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to scan, e.g., example.com |
No output schema declared.
No examples provided.
swagger_docs_creator ~106
Generate OpenAPI 3.0 documentation for an API endpoint. Provide the path, method, summary, and optionally parameters/requestBody/responses to get a complete OpenAPI spec fragment.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | — | Full description of the endpoint |
| method | string | yes | HTTP method (GET, POST, PUT, DELETE) |
| path | string | yes | API endpoint path (e.g. /api/users) |
| summary | string | yes | Short summary of what the endpoint does |
No output schema declared.
No examples provided.
tech_stack ~89
Detect the technology stack of any website. Analyzes HTTP headers and HTML to identify CMS, frameworks, languages, analytics, CDN, hosting, JavaScript libraries, and CSS frameworks. Free preview: GET https://tech-stack.apimesh.xyz/preview?url=... detects technologies from HTTP headers only
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL to analyze (e.g. https://example.com) |
No output schema declared.
No examples provided.
user_agent_analyzer ~54
Parse a User-Agent string into structured data: browser name/version, OS name/version, device type, and bot detection. Useful for analytics and request filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| ua | string | yes | The User-Agent string to parse |
No output schema declared.
No examples provided.
wallet_set_cap ~119
Set a spend cap on your wallet. Once the daily or monthly USDC limit is reached, further paid API calls return 429 before payment is attempted. Set limits to null to remove a cap.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your 0x wallet address |
| daily_limit_usd | number|null | yes | Max daily spend in USD (null = unlimited) |
| label | string|null | — | Friendly label (e.g. 'Claude Desktop') |
| monthly_limit_usd | number|null | yes | Max monthly spend in USD (null = unlimited) |
No output schema declared.
No examples provided.
wallet_usage ~69
Check your wallet's APIMesh spend and cap status. Returns daily/7d/30d spend totals, active spend cap with remaining budget, and recent requests. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Your 0x wallet address (e.g. 0xabc...def) |
No output schema declared.
No examples provided.
web_checker ~88
Check if a brand name is available across 5 domain TLDs (.com, .io, .xyz, .dev, .ai), GitHub, npm, PyPI, and Reddit in one call. Free preview: GET https://check.apimesh.xyz/preview?name=... returns .com availability only
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The brand or product name to check |
No output schema declared.
No examples provided.
web_configuration_audit ~43
Comprehensive paid audit with detailed scoring, grade, meta tags, and .env leak detection
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL to audit (http(s)://...) |
No output schema declared.
No examples provided.
web_misconfiguration_scan ~38
Run a comprehensive security misconfiguration scan against the specified URL
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Target URL to scan (http or https) |
No output schema declared.
No examples provided.
web_resource_validator ~77
Validate presence and correctness of common web resources (robots.txt, sitemap.xml, openapi.json, agent.json) for any domain. Returns availability status for the requested resource.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | The web resource to validate |
| url | string | yes | The website URL to validate resources for (e.g. https://example.com) |
No output schema declared.
No examples provided.
website_authenticity_assessment ~47
Comprehensive website authenticity assessment combining SSL cert validation, DNS records, redirect chain analysis, and server headers
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Target website URL (http(s)://...) |
No output schema declared.
No examples provided.
website_security_header_info ~84
Analyze security-related HTTP headers for any website. Checks Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, X-XSS-Protection, Referrer-Policy, and Permissions-Policy with issue detection.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website URL to analyze (e.g. https://example.com) |
No output schema declared.
No examples provided.
website_vulnerability_scan ~93
Comprehensive website security audit combining hostname analysis, SSL certificate validation, HTTP security headers, cookie security, and Content Security Policy analysis. Returns an overall security score (0-100) with actionable recommendations. Supports basic, detailed, and full scan levels.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | — | Scan detail level (default: full) |
| url | string | yes | The website URL to scan (e.g. https://example.com) |
No output schema declared.
No examples provided.
yaml_validator ~50
Validate YAML syntax and structure. Returns parsed result on success or detailed error with line/column on failure. Useful for CI pipelines and config file validation.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | The YAML string to validate |
No output schema declared.
No examples provided.