# Pyfile LLM & Data API (remote · pyfile-agent.taile3ff35.ts.net:8443)

Pay-per-call LLM chat plus data tools: DNS, crypto, Base gas, Wikipedia. x402 USDC or Lightning.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- remote · `pyfile-agent.taile3ff35.ts.net:8443`: 72/100 (this document), [markdown](https://verifymcp.io/servers/pyfile-toolkit-pyfile-llm/pyfile-agent.md), [page](https://verifymcp.io/servers/pyfile-toolkit-pyfile-llm/pyfile-agent)

## Channel facts

- Endpoint: `https://pyfile-agent.taile3ff35.ts.net:8443/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-27.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 796 tokens (~61/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http pyfile-toolkit-pyfile-llm 'https://pyfile-agent.taile3ff35.ts.net:8443/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pyfile-toolkit-pyfile-llm": {
      "url": "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pyfile-toolkit-pyfile-llm": {
      "type": "http",
      "url": "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pyfile-toolkit-pyfile-llm]
url = "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add pyfile-toolkit-pyfile-llm --url 'https://pyfile-agent.taile3ff35.ts.net:8443/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pyfile-toolkit-pyfile-llm:
    url: "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pyfile-toolkit-pyfile-llm": {
      "Transport": "http",
      "Url": "https://pyfile-agent.taile3ff35.ts.net:8443/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pyfile-toolkit-pyfile-llm -t streamable-http -u 'https://pyfile-agent.taile3ff35.ts.net:8443/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 72, +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.

### 2026-09-25 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 71, +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.

### 2026-09-22 (score 70, +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.

### 2026-09-20 (score 69, +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.

### 2026-09-19 (score 68, +1)

- [security regression] HSTS header: unverified → fail
- [security regression] DNSSEC: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] 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.
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.30
- [functional improvement] MCP protocol: unverified → pass

### 2026-09-18 (score 67, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] DNSSEC: fail → unverified
- [security regression] Stability: 0.23 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-15 (score 67, +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.

## MCP tools (13)

### `chat` (~36 tokens)

Ask an LLM a question. Returns a text completion.

Input parameters:

- `model` (string)
- `prompt` (string, required): The user prompt

### `dns_lookup` (~46 tokens)

Resolve a DNS record (A, AAAA, MX, TXT, NS).

Input parameters:

- `name` (string, required): Domain name, e.g. github.com
- `type` (string)

### `crypto_price` (~48 tokens)

Current USD prices for one or more coins (CoinGecko ids, comma-separated).

Input parameters:

- `ids` (string): Comma-separated CoinGecko ids, e.g. bitcoin,ethereum,nano

### `base_gas` (~21 tokens)

Current Base L2 gas price in wei and gwei.

### `wikipedia_summary` (~31 tokens)

Short summary of a Wikipedia article by title.

Input parameters:

- `title` (string, required): Article title, e.g. Bitcoin

### `brief` (~70 tokens)

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.

Input parameters:

- `focus` (string): Optional extra focus text.
- `topic` (string): Brief topic.

### `web_read` (~72 tokens)

Fetch any public web page and return its main readable content as clean Markdown (nav/ads stripped) for RAG and agent pipelines.

Input parameters:

- `max_chars` (integer): Max characters to return (default 20000).
- `url` (string, required): Public http(s) URL, e.g. https://example.com

### `ofac_sanctions_search` (~63 tokens)

Search the US Treasury OFAC SDN sanctions list by entity name (KYB/AML screening).

Input parameters:

- `limit` (integer): Max matches (default 10).
- `q` (string, required): Entity name to screen, e.g. a company name.

### `fda_lookup` (~63 tokens)

US FDA open data: drug adverse events, drug/food/device recalls, drug labels.

Input parameters:

- `kind` (string): Dataset.
- `limit` (integer): Max results (default 5).
- `q` (string): Optional search query, e.g. aspirin.

### `kyb_screening` (~55 tokens)

Composite counterparty due-diligence: OFAC SDN sanctions screening + GLEIF LEI + SEC EDGAR in one call. Requires a Bearer key.

Input parameters:

- `name` (string, required): Company name to screen.

### `enrich` (~77 tokens)

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.

Input parameters:

- `domain` (string): Domain, e.g. acme.com
- `name` (string): Company name, e.g. Acme

### `fair_draw` (~124 tokens)

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.

Input parameters:

- `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).

### `fair_pick` (~90 tokens)

Provably-fair selection of one winner from a list of candidates. For bounties with a single prize.

Input parameters:

- `candidates` (string, required): 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).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pyfile-toolkit-pyfile-llm/pyfile-agent#diagnostics

## Score history

- 2026-09-27: 72
- 2026-09-26: 72
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 67
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 64
- 2026-09-10: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://pyfile-agent.taile3ff35.ts.net:8443/mcp
- Repository: https://github.com/pyfile-toolkit/l402-llm-mcp
- Website: https://github.com/pyfile-toolkit/nano-llm-api
- Changelog RSS feed: https://verifymcp.io/servers/pyfile-toolkit-pyfile-llm/pyfile-agent.xml
- Changelog JSON feed: https://verifymcp.io/servers/pyfile-toolkit-pyfile-llm/pyfile-agent.json
- HTML version of this page: https://verifymcp.io/servers/pyfile-toolkit-pyfile-llm/pyfile-agent