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 · SCANNED SEP 21

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

+3 this week 68 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 458 tokens (~38/item across 12 items; 11 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "owenkingva-web-vulnhunt": {
      "url": "https://vulnhunt-agent-api-production.up.railway.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "owenkingva-web-vulnhunt": {
      "type": "http",
      "url": "https://vulnhunt-agent-api-production.up.railway.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.owenkingva-web-vulnhunt]
url = "https://vulnhunt-agent-api-production.up.railway.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "owenkingva-web-vulnhunt": {
      "type": "remote",
      "url": "https://vulnhunt-agent-api-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add owenkingva-web-vulnhunt --url 'https://vulnhunt-agent-api-production.up.railway.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  owenkingva-web-vulnhunt:
    url: "https://vulnhunt-agent-api-production.up.railway.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "owenkingva-web-vulnhunt": {
      "Transport": "http",
      "Url": "https://vulnhunt-agent-api-production.up.railway.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add owenkingva-web-vulnhunt -t streamable-http -u 'https://vulnhunt-agent-api-production.up.railway.app/mcp'
// mcp.json
{
  "mcpServers": {
    "owenkingva-web-vulnhunt": {
      "type": "http",
      "url": "https://vulnhunt-agent-api-production.up.railway.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +42
    • 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 −41
    • 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 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 +1
    • Stability: unverified → 0.03 functional
  • 10 Sept 26 63

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

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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 Verified 200
http (plaintext) http://vulnhunt-agent-api-production.up.railway.app/mcp HTTPS enforced 301 https://vulnhunt-agent-api-production.up.railway.app/mcp
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.

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 68 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?

No. We connected to VulnHunt Security Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VulnHunt Security Intelligence MCP server still maintained?

VulnHunt Security Intelligence is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.