Pyfile LLM & Data API
REMOTE · PYFILE-AGENT.TAILE3FF35.TS.NET:8443 · SCANNED SEP 27
Pay-per-call LLM chat plus data tools: DNS, crypto, Base gas, Wikipedia. x402 USDC or Lightning.
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 Security57
- 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 13 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 796 tokens (~61/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% 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 13 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Pyfile LLM & Data API MCP server?
Pyfile LLM & Data API is a hosted endpoint at https://pyfile-agent.taile3ff35.ts.net:8443/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 · pyfile-agent.taile3ff35.ts.net:8443
claude mcp add --transport http pyfile-toolkit-pyfile-llm 'https://pyfile-agent.taile3ff35.ts.net:8443/mcp'
{
"mcpServers": {
"pyfile-toolkit-pyfile-llm": {
"url": "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
}
}
} {
"servers": {
"pyfile-toolkit-pyfile-llm": {
"type": "http",
"url": "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
}
}
} [mcp_servers.pyfile-toolkit-pyfile-llm] url = "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pyfile-toolkit-pyfile-llm": {
"type": "remote",
"url": "https://pyfile-agent.taile3ff35.ts.net:8443/mcp",
"enabled": true
}
}
} openclaw mcp add pyfile-toolkit-pyfile-llm --url 'https://pyfile-agent.taile3ff35.ts.net:8443/mcp' --transport streamable-http
mcp_servers:
pyfile-toolkit-pyfile-llm:
url: "https://pyfile-agent.taile3ff35.ts.net:8443/mcp" {
"McpServers": {
"pyfile-toolkit-pyfile-llm": {
"Transport": "http",
"Url": "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
}
}
} assistant mcp add pyfile-toolkit-pyfile-llm -t streamable-http -u 'https://pyfile-agent.taile3ff35.ts.net:8443/mcp'
{
"mcpServers": {
"pyfile-toolkit-pyfile-llm": {
"type": "http",
"url": "https://pyfile-agent.taile3ff35.ts.net:8443/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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
- HSTS header: unverified → fail ▼ security
- DNSSEC: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 13 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
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 18 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.23 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 27 Sept 2026 · Probed https://pyfile-agent.taile3ff35.ts.net:8443/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pyfile-agent.taile3ff35.ts.net | CN=YE2,O=Let's Encrypt,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 53e539a1f6e544058feea1bba4956f9c859 |
| SANs: pyfile-agent.taile3ff35.ts.net | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 pyfile-agent.taile3ff35.ts.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| ts.net. | 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://pyfile-agent.taile3ff35.ts.net:8443/mcp | Verified | 200 | |
| http (plaintext) | http://pyfile-agent.taile3ff35.ts.net/mcp | HTTPS enforced | 302 | https://pyfile-agent.taile3ff35.ts.net/mcp |
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 →
base_gas ~21
Current Base L2 gas price in wei and gwei.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
brief ~70
Composite analyst brief: gathers live market facts (crypto prices, DeFi yields, Base block height) and returns an LLM-written brief with headline, key points, and a take. Requires a Bearer key.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Optional extra focus text. |
| topic | string | – | Brief topic. |
No output schema declared.
No examples provided.
chat ~36
Ask an LLM a question. Returns a text completion.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | – |
| prompt | string | yes | The user prompt |
No output schema declared.
No examples provided.
crypto_price ~48
Current USD prices for one or more coins (CoinGecko ids, comma-separated).
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | – | Comma-separated CoinGecko ids, e.g. bitcoin,ethereum,nano |
No output schema declared.
No examples provided.
dns_lookup ~46
Resolve a DNS record (A, AAAA, MX, TXT, NS).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Domain name, e.g. github.com |
| type | string | – | – |
No output schema declared.
No examples provided.
enrich ~77
One-call domain/company enrichment: DNS A records + certificate transparency names + GLEIF LEI + OFAC SDN + web snapshot, with an aggregate risk_summary. Requires a Bearer key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Domain, e.g. acme.com |
| name | string | – | Company name, e.g. Acme |
No output schema declared.
No examples provided.
fair_draw ~124
Provably-fair random integer from a committed seed (commit-reveal). Use for verifiable winner selection, raffles and allocations. Reveal the seed afterwards so anyone can reproduce the result.
| Name | Type | Req | Description |
|---|---|---|---|
| client_seed | string | – | Your own seed (keep it, it makes the draw verifiable). |
| max | integer | – | Maximum value (default 100). |
| min | integer | – | Minimum value (default 1). |
| nonce | string | – | A counter to get a new number from the same seed. |
| round | string | – | Round id (default 1). |
No output schema declared.
No examples provided.
fair_pick ~90
Provably-fair selection of one winner from a list of candidates. For bounties with a single prize.
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | string | yes | Comma-separated list of candidates, e.g. alice,bob,carol |
| client_seed | string | – | Your own seed. |
| nonce | string | – | Counter (default 1). |
| round | string | – | Round id (default 1). |
No output schema declared.
No examples provided.
fda_lookup ~63
US FDA open data: drug adverse events, drug/food/device recalls, drug labels.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Dataset. |
| limit | integer | – | Max results (default 5). |
| q | string | – | Optional search query, e.g. aspirin. |
No output schema declared.
No examples provided.
kyb_screening ~55
Composite counterparty due-diligence: OFAC SDN sanctions screening + GLEIF LEI + SEC EDGAR in one call. Requires a Bearer key.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Company name to screen. |
No output schema declared.
No examples provided.
ofac_sanctions_search ~63
Search the US Treasury OFAC SDN sanctions list by entity name (KYB/AML screening).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matches (default 10). |
| q | string | yes | Entity name to screen, e.g. a company name. |
No output schema declared.
No examples provided.
web_read ~72
Fetch any public web page and return its main readable content as clean Markdown (nav/ads stripped) for RAG and agent pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | Max characters to return (default 20000). |
| url | string | yes | Public http(s) URL, e.g. https://example.com |
No output schema declared.
No examples provided.
wikipedia_summary ~31
Short summary of a Wikipedia article by title.
| Name | Type | Req | Description |
|---|---|---|---|
| title | string | yes | Article title, e.g. Bitcoin |
No output schema declared.
No examples provided.
What is the Pyfile LLM & Data API MCP server?
Pyfile LLM & Data API is an MCP server listed in the public MCP registry as io.github.pyfile-toolkit/pyfile-llm. Pay-per-call LLM chat plus data tools: DNS, crypto, Base gas, Wikipedia. x402 USDC or Lightning. This page covers its hosted endpoint (https://pyfile-agent.taile3ff35.ts.net:8443/mcp).
Is the Pyfile LLM & Data API MCP server safe to use?
Pyfile LLM & Data API scores 72 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 Pyfile LLM & Data API MCP server expose?
Pyfile LLM & Data API exposes 13 tools: chat, dns_lookup, crypto_price, base_gas, wikipedia_summary, and 8 more. Their descriptions and schemas cost roughly 796 tokens of context every time the server is loaded.
Does the Pyfile LLM & Data API MCP server require authentication?
No. We connected to Pyfile LLM & Data API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pyfile LLM & Data API MCP server still maintained?
Pyfile LLM & Data API is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.