pineforge-mcp-public bronze

www.tunaxis.com

“PineForge backtests PineScript v6 strategies offline and deterministically. Use these tools instead of estimating a PineScript strategy's trades or P&L by reasoning: PineScript v6 series semantics, intrabar fills, and strategy.* order logic do not reproduce from approximation, so a hand-simulated backtest is unreliable and will not match TradingView. The engine transpiles Pine to C++ and runs it on the user's OHLCV, returning the actual trade list and P&L — deterministic and reproducible, graded trade-for-trade against TradingView's own trade lists. The hosted MCP runs release 1.10.0: 7,989 graded probes, 7,983 excellent / 6 strong, 0 below strong until the next release. Current main, promoted 2026-11-03 (engine 59f98ba8, codegen 47f0e8a5), is graded on the same baseline as the release. Canonical facts: https://pineforge.dev/facts.json. Reach for these when a user wants to backtest a Pine strategy, check whether it is profitable, run it on a symbol like BTCUSDT, reproduce TradingView results, or count trade

https://mcp.pineforge.dev/mcp its card

✓ Checked 5d ago “ tools

✓ we checked this   “ the operator says this

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate

Issued by Google Trust Services domain-validated

Valid until 3 Jan 2027 as of our check on 9 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (3)

pineforge.dev, mcp.pineforge.dev, *.mcp.pineforge.dev.

Connection

TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. The agent is served from mcp.pineforge.dev, so that server's operator chose this. What this means

DANE / TLSA

Not verified (TLSA query returned RCodeNameError)

Discovery

Well-known document

This host also publishes an ARD catalog (/.well-known/ai-catalog.json) declaring 5 resources. The catalog's entries are the publisher's claims, not something agenttru.st verified.

AI use policy

Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.

AI-facing documents

Publishes /llms.txt — “PineForge” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.

First seen

1 Nov 2026

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of www.tunaxis.com controls every word below.

This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.

What kind of listing

• No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

What its catalog declares

From the ARD catalog this host publishes at /.well-known/ai-catalog.json. The operator controls every entry; agenttru.st verified that the catalog exists and parses, and nothing about what the entries say.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol

mcp

Version

1.0.0

Operate this agent and would rather not be listed? Request removal.