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.

VulnHunt Security Intelligence

REMOTE · VULNHUNT-AGENT-API-PRODUCTION.UP.RAILWAY.APP

Read-only smart-contract security intelligence for autonomous agents.

0 this week 23 Trust /100

Last scanned (10 hours ago)

Scores higher than 8% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security11
Transport & Reachability0
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.

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
    • Endpoint reachability: not serving MCP → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
  • 29 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.60 → 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
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Sept 26 0
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 33 → 38 ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • Stability: unverified → 0.13 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Server version: 1.0.0 → 1.2.0 functional
    • New tool “gpufeed_compare_providers” functional
    • New tool “gpufeed_estimate_training” functional
    • New tool “gpufeed_get_availability” functional
    • New tool “gpufeed_get_cheapest” functional
    • New tool “gpufeed_get_history” functional
    • New tool “gpufeed_get_price_index” functional
    • New tool “gpufeed_recommend” functional
    • New tool “gpufeed_status” functional
  • 13 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Sept 26 0

    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 · Probed https://vulnhunt-agent-api-production.up.railway.app/mcp

TLS unreached
DNSSEC insecure

Validation of vulnhunt-agent-api-production.up.railway.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
railway.app. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vulnhunt-agent-api-production.up.railway.app/mcp Unreachable
http (plaintext) http://vulnhunt-agent-api-production.up.railway.app/mcp HTTPS enforced
MCP tools · 11 exposed · ~382 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
gpufeed_compare_providers ~35

Compare providers without treating missing data as unavailable.

NameTypeReqDescription
gpustringyes–
providersstring––

Structured output declared, but exposes no named fields.

No examples provided.

gpufeed_estimate_training ~45

Estimate GPU compute cost using observed prices, with assumptions exposed.

NameTypeReqDescription
countinteger––
gpustringyes–
hoursnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

gpufeed_get_availability ~35

Return observed GPU listings from free-first sources.

NameTypeReqDescription
countinteger––
gpustringyes–

Structured output declared, but exposes no named fields.

No examples provided.

gpufeed_get_cheapest ~42

Return the cheapest verified free-first GPU offer.

NameTypeReqDescription
countinteger––
gpustringyes–
hoursnumber––

Structured output declared, but exposes no named fields.

No examples provided.

gpufeed_get_history ~46

Return persisted verified GPU price observations.

NameTypeReqDescription
daysinteger––
gpustringyes–
limitinteger––
providerstring––

Structured output declared, but exposes no named fields.

No examples provided.

gpufeed_get_price_index ~34

Return descriptive statistics over persisted GPU observations.

NameTypeReqDescription
daysinteger––
gpustringyes–

Structured output declared, but exposes no named fields.

No examples provided.

gpufeed_recommend ~44

Return a bounded lowest-observed-cost recommendation for further verification.

NameTypeReqDescription
countinteger––
gpustringyes–
hoursnumber––

Structured output declared, but exposes no named fields.

No examples provided.

gpufeed_status ~25

Return GPUFEED scope, guardrail, metering and provider status.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

vulnhunt_chains ~15

List supported chains.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

vulnhunt_decision ~38

Return a bounded free decision packet for an EVM contract.

NameTypeReqDescription
addressstringyes–
chain_idintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

vulnhunt_payment_resources ~23

Return the machine-readable paid resource catalog and x402 terms.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the VulnHunt Security Intelligence MCP server?

VulnHunt Security Intelligence is a hosted endpoint at https://vulnhunt-agent-api-production.up.railway.app/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 · vulnhunt-agent-api-production.up.railway.app

# add to Claude Code
claude mcp add --transport http owenkingva-web-vulnhunt 'https://vulnhunt-agent-api-production.up.railway.app/mcp'
Common questions

What is the VulnHunt Security Intelligence MCP server?

VulnHunt Security Intelligence is an MCP server listed in the public MCP registry as io.github.owenkingva-web/vulnhunt. Read-only smart-contract security intelligence for autonomous agents. This page covers its hosted endpoint (https://vulnhunt-agent-api-production.up.railway.app/mcp).

Is the VulnHunt Security Intelligence MCP server safe to use?

VulnHunt Security Intelligence 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 VulnHunt Security Intelligence MCP server expose?

VulnHunt Security Intelligence exposes 11 tools: vulnhunt_decision, vulnhunt_payment_resources, vulnhunt_chains, gpufeed_get_cheapest, gpufeed_get_availability, and 6 more. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.

Does the VulnHunt Security Intelligence MCP server require authentication?

Its publisher declares no required credentials for VulnHunt Security Intelligence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the VulnHunt Security Intelligence MCP server still maintained?

VulnHunt Security Intelligence is still listed in the MCP registry, though our most recent checks did not reach this channel. 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.