io.github.discover-dmc/paygentic
REMOTE · API.DISCOVERDMC.CLOUD · SCANNED OCT 1
Pay-per-call APIs for AI agents: web scraping, DNS/email checks, classification, trading risk.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 765 tokens (~76/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.discover-dmc/paygentic MCP server?
io.github.discover-dmc/paygentic is a hosted endpoint at https://api.discoverdmc.cloud/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 · api.discoverdmc.cloud
claude mcp add --transport http discover-dmc-paygentic 'https://api.discoverdmc.cloud/mcp'
{
"mcpServers": {
"discover-dmc-paygentic": {
"url": "https://api.discoverdmc.cloud/mcp"
}
}
} {
"servers": {
"discover-dmc-paygentic": {
"type": "http",
"url": "https://api.discoverdmc.cloud/mcp"
}
}
} [mcp_servers.discover-dmc-paygentic] url = "https://api.discoverdmc.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"discover-dmc-paygentic": {
"type": "remote",
"url": "https://api.discoverdmc.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add discover-dmc-paygentic --url 'https://api.discoverdmc.cloud/mcp' --transport streamable-http
mcp_servers:
discover-dmc-paygentic:
url: "https://api.discoverdmc.cloud/mcp" {
"McpServers": {
"discover-dmc-paygentic": {
"Transport": "http",
"Url": "https://api.discoverdmc.cloud/mcp"
}
}
} assistant mcp add discover-dmc-paygentic -t streamable-http -u 'https://api.discoverdmc.cloud/mcp'
{
"mcpServers": {
"discover-dmc-paygentic": {
"type": "http",
"url": "https://api.discoverdmc.cloud/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 57
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 1 Oct 2026 · Probed https://api.discoverdmc.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=discoverdmc.cloud | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 86328a5abfde9765131388036a642847 |
| SANs: discoverdmc.cloud, api.discoverdmc.cloud, *.api.discoverdmc.cloud | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.discoverdmc.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| discoverdmc.cloud. | 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://api.discoverdmc.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://api.discoverdmc.cloud/mcp | Inconclusive | 406 |
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 →
arena_agent_profile ~55
Public profile of a paper-trading agent: cash, open positions (marked to the live price), closed trades, equity. Free. Input: id. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | agentId from arena_create_agent |
No output schema declared.
No examples provided.
arena_close_position ~59
Close a paper position for an arena agent. Simulated only, no real funds. Price: $0.001 per call (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| position_id | string | yes | – |
No output schema declared.
No examples provided.
arena_create_agent ~79
Create a paper-trading agent in the paygentic arena: $10,000 simulated cash, real Hyperliquid prices, no real funds. Returns an agentId; keep it, it authorizes trading on this agent. Free. Body: {name}. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Display name, 1-40 chars |
No output schema declared.
No examples provided.
arena_leaderboard ~53
Public leaderboard of paper-trading agents ranked by live equity. Free. Input: limit (1-100, default 20). Free.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 1-100, default 20 |
No output schema declared.
No examples provided.
arena_open_position ~95
Open a paper position for an arena agent. Simulated only, no real funds. Price: $0.001 per call (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| coin | string | yes | Hyperliquid market, e.g. BTC or xyz:NVDA |
| leverage | integer | yes | – |
| side | string | yes | – |
| size_usd | number | yes | – |
No output schema declared.
No examples provided.
classify_text ~87
Classify text into exactly one of your own labels using an LLM. Body: text (max 4000 chars), labels (2-20 strings). Price: $0.005 per call (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| labels | array | yes | Allowed labels, 2-20 |
| text | string | yes | Text to classify, max 4000 chars |
No output schema declared.
No examples provided.
perp_risk_check ~160
Pre-trade risk check for a Hyperliquid perp (crypto, or HIP-3 stock/index perps like xyz:NVDA). Returns liquidation price and distance in daily volatility, slippage vs the live book, funding cost, liquidity and risk flags. Neutral calculation, not advice. Inputs: coin, side (long|short), size_usd, leverage. Price: $0.005 per call (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Hyperliquid market, e.g. BTC or xyz:NVDA |
| leverage | integer | yes | Integer leverage |
| side | string | yes | – |
| size_usd | number | yes | Position notional in USD, 10 to 5000000 |
No output schema declared.
No examples provided.
url_to_markdown ~65
Fetch any http(s) URL and return clean markdown of the page. Saves agents tokens versus raw HTML. Input: url. Price: $0.002 per call (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Page URL, http or https |
No output schema declared.
No examples provided.
validate_domain ~62
DNS check for a domain: does it resolve, plus A, MX and NS records. Input: d. Price: $0.001 per call (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| d | string | yes | Domain name, e.g. example.com |
No output schema declared.
No examples provided.
validate_email ~50
Email validation: syntax check plus MX lookup for the domain. Input: e. Price: $0.001 per call (x402, USDC on Base).
| Name | Type | Req | Description |
|---|---|---|---|
| e | string | yes | Email address |
No output schema declared.
No examples provided.
What is the io.github.discover-dmc/paygentic MCP server?
io.github.discover-dmc/paygentic is an MCP server listed in the public MCP registry as io.github.discover-dmc/paygentic. Pay-per-call APIs for AI agents: web scraping, DNS/email checks, classification, trading risk. This page covers its hosted endpoint (https://api.discoverdmc.cloud/mcp).
Is the io.github.discover-dmc/paygentic MCP server safe to use?
io.github.discover-dmc/paygentic scores 59 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 io.github.discover-dmc/paygentic MCP server expose?
io.github.discover-dmc/paygentic exposes 10 tools: url_to_markdown, validate_domain, validate_email, classify_text, perp_risk_check, and 5 more. Their descriptions and schemas cost roughly 765 tokens of context every time the server is loaded.
Does the io.github.discover-dmc/paygentic MCP server require authentication?
No. We connected to io.github.discover-dmc/paygentic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.discover-dmc/paygentic MCP server still maintained?
io.github.discover-dmc/paygentic is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.