Skip to content

MCP servers › xyz.apexfaucet › apex-dev

MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19

apex-dev MCP server

Registry name xyz.apexfaucet/apex-dev

by apexfaucet.xyz · domain (the registry's namespace rule)Website ↗

Dev & Agent Trust MCP: Agent Firewall, Work Grader, Launch Audit, npm/PyPI CVEs & PDF tools. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-19version 1.3.0streamable HTTP26 tools

Summary

xyz.apexfaucet/apex-dev is a remote MCP server listed in the official MCP registry at version 1.3.0, under the namespace of the domain apexfaucet.xyz. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 26 tools, 4 resources and 5 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
26
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (apexfaucet.xyz), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.3.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
1.3.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-19 (earliest version still in the registry; older removed versions would be earlier)
Version history
4 versions listed, all on 2026-11-19; 4 in the 90 days before the 2026-11-19 snapshot.
Most recent 4 versions
  • 1.3.0 · 2026-11-19
  • 1.2.0 · 2026-11-19
  • 1.1.0 · 2026-11-19
  • 1.0.0 · 2026-11-19
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-18, listed on 2026-11-19 with version 1.3.0 (published 2026-11-19).

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19.

What it is

What does this server offer?

Observed inventory
26tools
4resources
5prompts

None of its 26 tools are described as changing anything. For 26 the reading was uncertain, so no mark is shown.

  • agent_firewallon 2 other servers

    “Unified orchestrator access-control & pre-payment firewall for autonomous AI agents: enforces per-tx/daily USD spend caps, human-approval threshold, allowlists/denylists, HTTPS/phishing URL check, pr…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    14 inputs
    • agentIdstring“Optional caller/agent identifier recorded in signed claims.”
    • actionstring“Proposed autonomous action (default: pay).”
    • amount_usdnumber“Optional proposed USD amount.”
    • max_tx_usdnumber“Optional per-transaction USD cap.”
    • daily_limit_usdnumber“Optional daily USD budget cap.”
    • spent_today_usdnumber“Optional USD already spent today.”
    • human_above_usdnumber“Optional autonomous spend threshold above which HOLD_FOR_HUMAN is returned.”
    • urlstring“Optional target URL to check for HTTPS & phishing signals.”
    • payeestring“Optional target wallet address or merchant identifier.”
    • promptstring“Optional inbound prompt text to scan for injection/hijack.”
    • payloadTextstring“Optional outbound payload text to scan for secret/key/PII exfiltration.”
    • policyobject“Optional full policy object ({ maxTxUsd, dailyLimitUsd, spentTodayUsd, humanApprovalAboveUsd, allowlist, denylist, allowedActions, allowedChains, allowedTools,…”
    • targetobject“Optional full target object ({ amountUsd, payee, url, chain, tool, prompt, payloadText }).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • “Grade any AI agent work deliverable before releasing escrow (ERC-8183 / G2 Jobs / MCP): checks JSON/schema validity, anti-refusal/stub quality, embedded indirect prompt injection, secret/PII leakage,…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    10 inputs, 2 required
    • taskstringrequired“Task specification the worker agent was hired to complete.”
    • outputstringrequired“Deliverable output produced by the worker agent.”
    • expectedFormatstring“Optional expected output format.”
    • requiredFieldsarray“Optional required JSON keys when output is JSON.”
    • jsonSchemaobject“Optional JSON Schema object to validate JSON output against.”
    • rubricstring“Optional evaluation criteria.”
    • useAiJudgeboolean“Optional: enable Workers AI rubric judge alongside deterministic checks.”
    • jobIdstring“Optional escrow job ID bound into signed claims.”
    • providerstring“Optional worker wallet/ID bound into signed claims.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • veritas_notaryon 2 other servers

    “Hash-chained Proof-of-Execution Notary for autonomous AI agents: links any workflow step to an optional parentReceiptHash, runs deterministic security/integrity checks (prompt injection, secret/PII l…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 2 required
    • agentIdstringrequired“Unique identifier, wallet, or domain of the executing AI agent.”
    • outputstringrequired“Step deliverable/output to hash-notarize and integrity-check (raw text is never stored).”
    • stepTypestring“Workflow step type (policy_gate, data_witness, tool_execution, work_deliverable, trade_signal, escrow_release, audit_cert, workflow_step).”
    • parentReceiptHashstring“Optional prior Veritas receiptHash to chain steps into a Merkle/hash-chain.”
    • expectedFormatstring“Optional format validation.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • agent_crediton 2 other servers

    “Machine Credit Bureau (300-950 autonomous AI agent credit & trust score): fuses Veritas Proof-of-Execution history and live domain hygiene to return an Ed25519-signed AgentCreditReport with directly …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • agentIdstringrequired“AI agent ID, wallet address, or public domain to score.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • agent_launch_auditon 2 other servers

    “Comprehensive 1-call production launch readiness audit for any AI agent, MCP server, or x402 API domain: fuses A2A/MCP/x402/JWKS/llms.txt discovery grading, HTTPS/phishing threat checks, tech-stack d…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • domainstringrequired“Domain or URL of the AI agent / MCP server / x402 API to audit (e.g.”
    • x402_urlstring“Optional specific x402 endpoint URL on that domain to live-probe for delivery-score.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • html_sanitizeon 7 other servers

    “Sanitize untrusted HTML before feeding to an LLM or UI: strips XSS scripts/iframes/on* handlers/javascript: URIs, detects & removes hidden CSS prompt-injection blocks, and returns safeHtml, clean Mar…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • htmlstringrequired“Untrusted HTML to sanitize and convert to safe Markdown (up to 256 KB).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • package_auditon 11 other servers

    “npm and PyPI package security and supply-chain audit: checks registry existence (catches hallucinated packages), deprecation, install scripts, age, and Google OSV.dev CVEs/GHSAs with SAFE/CAUTION/RIS…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • namestringrequired“Package name on npm or PyPI (e.g.”
    • ecosystemstring“Registry: npm (default) or pypi.”
    • versionstring“Optional exact version to audit against OSV.dev.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • github_repo_intelon 2 other servers

    “GitHub repository info and maintenance health intelligence: stars, forks, open issues, primary language, license, latest release, days since last push, 0-100 health score, and ACTIVE/MAINTAINED/STALE…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • repostringrequired“GitHub owner/name or URL (e.g.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • “CVE vulnerability lookup by CVE ID or keyword combining official NVD 2.0, OSV.dev affected package versions, and CISA Known Exploited Vulnerabilities (KEV).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • cvestring“Exact CVE ID (e.g.”
    • qstring“Keyword search query (e.g.”
    • limitnumber“Optional max results for keyword search (1-20, default 5).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • tech_stack_detecton 2 other servers

    “Detect the technology stack of any public website (45+ CDNs, hosting, Next.js/React/Vue/Astro frameworks, CMS, analytics, Stripe/payments, auth, security).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • urlstringrequired“Public website URL or domain to fingerprint (e.g.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • url_threat_checkon 3 other servers

    “Check any URL for phishing, brand impersonation, Punycode/IDN homographs, credential tricks, executable downloads, DNS resolution, and redirect chain risk (SAFE/CAUTION/RISKY).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • urlstringrequired“Full http(s) URL to check for phishing and threat signals.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • json_toolboxon 3 other servers

    “Deterministic JSON Schema validator, structural JSON diff, dot-path query, flatten/unflatten, and JSON<->CSV converter.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 1 required
    • opstringrequired“Operation: validate, diff, flatten, unflatten, to_csv, from_csv, or query.”
    • data“Primary JSON value or JSON string.”
    • schema“JSON Schema object when op=validate.”
    • b“Second JSON value when op=diff.”
    • pathstring“Dot/bracket path when op=query.”
    • csvstring“CSV text when op=from_csv.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
Show 14 more tools
  • “Clean and repair broken JSON from LLM outputs or scraped text (fences, trailing commas, single quotes, bare keys, Python literals, truncated brackets) ($0.001).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • textstringrequired“Broken or fenced JSON text to repair (up to 32000 chars)”
    • paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
  • “Generate a scannable ISO 18004 QR code (SVG vector and/or base64 PNG data URI) for any URL, wallet address, payment URI, or text up to 271 bytes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    5 inputs, 1 required
    • textstringrequired“Text, URL, wallet address, or payment URI to encode.”
    • eccstring“Optional error correction level: L, M (default), Q, or H.”
    • formatstring“Optional output format: svg (default), png, or both.”
    • sizenumber“Optional image size in pixels (64-1024, default 256).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • pdf_to_markdownon 9 other servers

    “Convert any public PDF URL or base64 PDF into clean LLM-ready Markdown with headings, bullet formatting, page markers, title/author metadata, and word count.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • urlstring“Public http(s) URL of a PDF document (or pass pdfBase64).”
    • pdfBase64string“Optional base64-encoded PDF file (up to 6 MB).”
    • max_pagesnumber“Optional max pages to extract (1-150).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • markdown_to_pdfon 6 other servers

    “Convert Markdown (headings, GFM tables, fenced code blocks, lists, links) into a styled print-ready base64 PDF via hermetic sandboxed headless Chrome.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    7 inputs, 1 required
    • markdownstringrequired“Markdown document to render into PDF (up to 256 KB).”
    • titlestring“Optional document title.”
    • formatstring“Optional paper format: A4 (default), Letter, Legal, Tabloid, A3, or A5.”
    • themestring“Optional typography theme: clean (default), editorial, or compact.”
    • marginstring“Optional margin preset: none, compact, normal (default), or wide.”
    • landscapeboolean“Optional landscape orientation.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • “Convert raw HTML markup into a print-ready base64 PDF via hermetic sandboxed headless Chrome (no external network requests).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    6 inputs, 1 required
    • htmlstringrequired“HTML markup to render into PDF (up to 512 KB; inline CSS and data: URIs supported).”
    • formatstring“Optional paper format: A4 (default), Letter, Legal, Tabloid, A3, or A5.”
    • landscapeboolean“Optional: render landscape orientation when true (default false).”
    • marginstring“Optional margin preset: none, compact, normal (default), or wide.”
    • printBackgroundboolean“Optional: print CSS backgrounds (default true).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • “Parse any public RSS 2.0, Atom 1.0, or JSON Feed URL into clean structured JSON items with ISO timestamps, authors, categories, and plain-text summaries.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs, 1 required
    • urlstringrequired“Public http(s) URL of an RSS, Atom, or JSON Feed.”
    • limitnumber“Optional max items to return (1-50, default 20).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • “Official ECB foreign exchange currency converter across 30+ major fiat currencies (USD, EUR, GBP, JPY, CHF, CAD, AUD, CNY, INR, BRL, etc.).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • fromstringrequired“3-letter source currency code (e.g.”
    • tostring“Optional target 3-letter currency code or comma-separated list (e.g.”
    • amountnumber“Optional amount to convert (default 1).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • “WHOIS and authoritative IANA RDAP domain registration lookup (registrar, IANA ID, creation/update/expiry dates, age in days, DNSSEC, EPP statuses, nameservers).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • domainstringrequired“Public domain name to query (e.g.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • ip_geolocateon 4 other servers

    “IP geolocation and ASN lookup for any public IPv4, IPv6, or hostname (country, region, city, lat/lon, timezone, ISP, org, ASN).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • ipstringrequired“Public IPv4/IPv6 address or hostname (e.g.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • agent_card_gradeon 3 other servers

    “Audit and grade any AI agent domain or A2A agent card (/.well-known/agent-card.json, agent.json, mcp-server-card.json, x402, /llms.txt) with a 0-100 score, A+-F grade, and concrete fixes.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • domainstringrequired“Public domain or /.well-known/agent-card.json URL to audit.”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • x402_price_compson 2 other servers

    “Live x402 market price comparison across 38,000+ indexed Coinbase Bazaar, Circle, and Arc paid APIs: min/p25/median/p75/max USD, suggested competitive price, and top competing endpoints.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 1 required
    • qstringrequired“Category, task, or keywords to benchmark (e.g.”
    • networkstring“Optional network filter (e.g.”
    • limitnumber“Optional max comparable endpoints (1-30, default 12).”
    • paymentstring“signed x402 payment payload (PAYMENT-SIGNATURE).”
  • delivery_scoreon 2 other servers

    “Free sample: https://apexfaucet.xyz/delivery-score?url=https://apexfaucet.xyz/api/x402/page-markdown ($0.003).”

    2 inputs, 1 required
    • urlstringrequired“https x402 URL to score.”
    • paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
  • prompt_guardon 4 other servers

    “Scan untrusted text for prompt injection, jailbreak attempts, delimiter spoofing, wallet exfiltration, and encoded payloads ($0.001).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • textstringrequired“Untrusted text or prompt payload to scan (up to 32000 chars)”
    • paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”
  • “Detect and redact private keys, API tokens, JWTs, emails, IBANs, SSNs, phones, IPs, and Luhn-validated payment cards before LLM logging or sharing ($0.001).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    2 inputs, 1 required
    • textstringrequired“Text to scan and redact PII/secrets from (up to 32000 chars)”
    • paymentstring“a signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 105
Tools with a description
100% of 26
Typical description length
354 characters

The tool set

Counted from the listing

Tools
26
Size of the list
about 6,680 tokens for an agent to load (characters ÷ 4)
Naming
26 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 26 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-19 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://apexfaucet.xyz/api/mcp/dev
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "apex-dev": {
      "url": "https://apexfaucet.xyz/api/mcp/dev"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "apex-dev": {
      "type": "http",
      "url": "https://apexfaucet.xyz/api/mcp/dev"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"apex-dev","type":"http","url":"https://apexfaucet.xyz/api/mcp/dev"}'
Claude Code
claude mcp add --transport http apex-dev https://apexfaucet.xyz/api/mcp/dev
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "apex-dev": {
      "type": "streamableHttp",
      "url": "https://apexfaucet.xyz/api/mcp/dev",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "apex-dev": {
      "httpUrl": "https://apexfaucet.xyz/api/mcp/dev"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.apex-dev]
url = "https://apexfaucet.xyz/api/mcp/dev"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "apex-dev": {
      "url": "https://apexfaucet.xyz/api/mcp/dev"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://apexfaucet.xyz/api/mcp/dev --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint apexfaucet.xyz/api/mcp/devSession openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about xyz.apexfaucet/apex-dev

Answered from the data above

Who publishes xyz.apexfaucet/apex-dev?

The registry ties the namespace xyz.apexfaucet to the domain apexfaucet.xyz; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does xyz.apexfaucet/apex-dev need an API key or sign-in?

It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.

Has xyz.apexfaucet/apex-dev been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (no operator permission)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-19
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 624 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 26 tools, 4 resources, 5 prompts.
  4. 8,392 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-19
MCP capability
tools
our test · 2026-11-19
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “xyz.apexfaucet/apex-dev: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/xyz.apexfaucet/apex-dev

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/xyz.apexfaucet/apex-dev)](https://protocolprobe.com/mcp/servers/xyz.apexfaucet/apex-dev)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology