io.github.mbeato/apimesh

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  fail25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  tool "web_checker" description: URL on a cheap/abused TLD (check.apimesh.xyz) — postmark-mcp used giftshop.club. tool "microservice_health_check" description: URL on a cheap/abused TLD (microservice-health-check.apimesh.xyz) — postmark-mcp used giftshop.club. tool "core_web_vitals" description: URL on a cheap/abused TLD (core-web-vitals.apimesh.xyz) — postmark-mcp used giftshop.club. tool "security_headers" description: URL on a cheap/abused TLD (security-headers.apimesh.xyz) — postmark-mcp used giftshop.club. tool "redirect_chain" description: URL on a cheap/abused TLD (redirect-chain.apimesh.xyz) — postmark-mcp used giftshop.club. tool "email_security" description: URL on a cheap/abused TLD (email-security.apimesh.xyz) — postmark-mcp used giftshop.club. tool "seo_audit" description: URL on a cheap/abused TLD (seo-audit.apimesh.xyz) — postmark-mcp used giftshop.club. tool "indexability_checker" description: URL on a cheap/abused TLD (indexability.apimesh.xyz) — postmark-mcp used giftshop.club. tool "brand_assets" description: URL on a cheap/abused TLD (brand-assets.apimesh.xyz) — postmark-mcp used giftshop.club. tool "email_verify" description: URL on a cheap/abused TLD (email-verify.apimesh.xyz) — postmark-mcp used giftshop.club. tool "tech_stack" description: URL on a cheap/abused TLD (tech-stack.apimesh.xyz) — postmark-mcp used giftshop.club. tool "tech_stack" param "url" description: off-vendor URL in a description (example.com); capability text should not name where data goes. tool "web_resource_validator" param "url" description: off-vendor URL in a description (example.com); capability text should not name where data goes. tool "website_security_header_info" param "url" description: off-vendor URL in a description (example.com); capability text should not name where data goes. tool "website_vulnerability_scan" param "url" description: off-vendor URL in a description (example.com); capability text should not name where data goes. tool "ssl_tls_configuration_ranker" param "url" description: off-vendor URL in a description (...); capability text should not name where data goes. tool "cross_origin_resource_policymapper" param "baseUrl" description: off-vendor URL in a description (example.com); capability text should not name where data goes.

• Supply chain

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  repository linkage verified

• Credential hygiene

  fail15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  tool "mock_jwt_generator" has a secret-shaped input parameter "secret" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  pass15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  unscannable10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  no prior version to diff (first sight of io.github.mbeato/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

• Transport config

  unscannable10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.