Freysa Security
REMOTE · ECONOMIC-AGENT-369.FREYSA.DEV · SCANNED SEP 3
Security intelligence for AI agents. 27 x402 endpoints: honeypot, forensics, CAPTCHA, preflight.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Freysa Security MCP server?
Freysa Security is a hosted endpoint at https://economic-agent-369.freysa.dev/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 · economic-agent-369.freysa.dev
claude mcp add --transport http dev-freysa-economic-agent-369-freysa-intelligenc 'https://economic-agent-369.freysa.dev/mcp'
{
"mcpServers": {
"dev-freysa-economic-agent-369-freysa-intelligenc": {
"url": "https://economic-agent-369.freysa.dev/mcp"
}
}
} {
"servers": {
"dev-freysa-economic-agent-369-freysa-intelligenc": {
"type": "http",
"url": "https://economic-agent-369.freysa.dev/mcp"
}
}
} [mcp_servers.dev-freysa-economic-agent-369-freysa-intelligenc] url = "https://economic-agent-369.freysa.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-freysa-economic-agent-369-freysa-intelligenc": {
"type": "remote",
"url": "https://economic-agent-369.freysa.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-freysa-economic-agent-369-freysa-intelligenc --url 'https://economic-agent-369.freysa.dev/mcp' --transport streamable-http
mcp_servers:
dev-freysa-economic-agent-369-freysa-intelligenc:
url: "https://economic-agent-369.freysa.dev/mcp" {
"McpServers": {
"dev-freysa-economic-agent-369-freysa-intelligenc": {
"Transport": "http",
"Url": "https://economic-agent-369.freysa.dev/mcp"
}
}
} assistant mcp add dev-freysa-economic-agent-369-freysa-intelligenc -t streamable-http -u 'https://economic-agent-369.freysa.dev/mcp'
{
"mcpServers": {
"dev-freysa-economic-agent-369-freysa-intelligenc": {
"type": "http",
"url": "https://economic-agent-369.freysa.dev/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.
- 3 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Sept 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Aug 26 −4
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Aug 26 −5
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Aug 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 27 Aug 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +17
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Sept 2026 · Probed https://economic-agent-369.freysa.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of economic-agent-369.freysa.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| economic-agent-369.freysa.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://economic-agent-369.freysa.dev/mcp | Unreachable | ||
| http (plaintext) | http://economic-agent-369.freysa.dev/mcp | HTTPS enforced |
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 →
captcha.solve ~146
Solve CAPTCHA challenges. Supports image CAPTCHAs, reCAPTCHA v2, and Turnstile. Submit base64 image or image URL. Returns solved text in seconds. 99% accuracy. Power your web automation agents with CAPTCHA bypass. $0.01 per solve.
| Name | Type | Req | Description |
|---|---|---|---|
| captcha_type | string | – | Type of CAPTCHA to solve: text (image text), recaptcha_v2 (Google reCAPTCHA), or turnstile (Cloudflare) |
| image_base64 | string | – | Base64-encoded CAPTCHA image data (alternative to image_url) |
| image_url | string | – | URL of CAPTCHA image to solve. Example: https://example.com/captcha.png |
| Name | Type | Req | Description |
|---|---|---|---|
| captcha_type | string | – | Type of CAPTCHA solved |
| confidence | number | – | Confidence score 0.0 to 1.0 |
| method | string | – | Method used capsolver or tesseract-ocr |
| solved | string | – | Solved CAPTCHA text or token |
No examples provided.
security.address ~69
Check if a wallet address is safe. Returns scam indicators risk score 0 to 100 and recommendation. Checks sanction lists phishing links and suspicious patterns. Used by trading agents before sending funds.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to analyze for scam indicators |
| chain | string | – | Blockchain network |
| Name | Type | Req | Description |
|---|---|---|---|
| eth_balance | string | – | ETH balance |
| is_contract | boolean | – | Whether address is a contract |
| recommendation | string | – | safe_caution_block |
| risk_score | number | – | Risk score 0 to 100 |
| scam_indicators | array | – | Suspicious patterns found |
| tx_count | number | – | Transaction count |
No examples provided.
security.approval ~79
Check if a token approval is safe. Detects dangerous spenders unlimited allowance risks and malicious patterns. Every output cites block evidence. Use before signing any approve transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain network |
| spender_address | string | yes | Spender address to check for approval risk |
| token_address | string | yes | Token contract address |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | Evidence supporting recommendation |
| is_dangerous | boolean | – | Whether approval is dangerous |
| recommendation | string | – | safe_caution_block |
| risk_score | number | – | Approval risk score 0 to 100 |
No examples provided.
security.buy_decision ~77
BUY_AVOID_CAUTION decision for any token. Combines honeypot check contract risk liquidity analysis and holder concentration. Returns structured decision with confidence score and evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| capital | number | – | Capital in USD for impact calculation |
| chain | string | – | Blockchain network |
| token_address | string | yes | Token address to evaluate |
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | Confidence score 0 to 100 percent |
| decision | string | – | Trading decision |
| evidence | array | – | Supporting evidence |
| risk_score | number | – | Risk score 0 to 100 |
No examples provided.
security.contract ~64
Smart contract risk assessment. Checks if verified upgradeable has dangerous functions proxy patterns owner privileges and known exploit vectors. Deterministic on-chain analysis no LLM hallucination.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain network |
| contract_address | string | yes | Smart contract address to audit |
| Name | Type | Req | Description |
|---|---|---|---|
| has_dangerous_functions | boolean | – | Whether dangerous functions exist |
| is_upgradeable | boolean | – | Whether contract is upgradeable |
| is_verified | boolean | – | Whether contract source is verified |
| recommendation | string | – | safe_caution_block |
| risk_score | number | – | Risk score 0 to 100 |
No examples provided.
security.honeypot ~86
Check if a token is a honeypot using real eth_call sell simulation. Detects if you can actually sell the token. Returns sell restrictions buy_sell tax blacklist status and evidence with block number. Deterministic no AI hallucination.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain network |
| token_address | string | yes | Token contract address to check for honeypot characteristics |
| Name | Type | Req | Description |
|---|---|---|---|
| block_number | number | – | Block number at analysis time |
| buy_tax | number | – | Buy tax percentage 0 if none |
| can_sell | boolean | – | Whether sell simulation passed |
| evidence | array | – | Evidence chain |
| is_honeypot | boolean | – | Whether the token is a honeypot |
| risk | string | – | Risk level safe_low_medium_high_critical |
| risk_score | number | – | Numeric risk score 0 to 100 |
| sell_tax | number | – | Sell tax percentage 0 if none |
No examples provided.
security.pre_trade ~89
Full pre-trade risk check. Checks token contract wallet liquidity slippage and price impact in one call. Includes amount-based impact calculation. For agents that need to know if a trade is safe.
| Name | Type | Req | Description |
|---|---|---|---|
| capital | number | – | Capital amount in USD |
| chain | string | – | Blockchain network |
| token_address | string | yes | Token address |
| trader_wallet | string | – | Trader wallet address |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | – | PROCEED_CAUTION_ABORT |
| flags | array | – | Risk flags |
| price_impact_pct | number | – | Estimated price impact percentage |
| risk_score | number | – | Composite risk score 0 to 100 |
No examples provided.
security.preflight ~121
One-call comprehensive safety check for AI agents. Checks target contract token and wallet together. Returns PROCEED_CAUTION_ABORT decision with evidence. Designed for autonomous agents executing complex workflows. Most thorough analysis at $0.50.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain network |
| interaction_type | string | – | Type of interaction: swap_buy_sell_approve_stake |
| target_address | string | yes | Target contract or token address to evaluate |
| trader_wallet | string | – | Wallet address performing the interaction |
| value | number | – | Transaction value in ETH |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | – | Safety decision |
| evidence | array | – | Evidence chain |
| risk_score | number | – | Overall risk score 0 to 100 |
| warnings | array | – | Specific warnings |
No examples provided.
security.score ~108
Quick token security score 0-100. Returns SAFE_CAUTION_DANGER decision plus risk flags. Fastest decision at $0.01. For agents that need one number before trading.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain network. Options: base, ethereum, polygon |
| token_address | string | yes | Token contract address to evaluate. Example: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | – | Trading decision |
| evidence | array | – | Evidence chain supporting the decision |
| flags | array | – | Risk flags e.g. cannot_sell has_mint_function |
| score | number | – | Security score 0-100 higher is safer |
| time_ms | number | – | Response time in milliseconds |
No examples provided.
security.trial ~90
Free trial - 3 security/reasoning calls per day. No payment needed. Try security_score, honeypot_check, or address_risk.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Which tool to try for free |
| chain | string | – | Blockchain network |
| prompt | string | yes | Token address or question for the free trial |
| wallet | string | yes | Your wallet address for rate limiting |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | – | Tool result |
No examples provided.
security.wallet ~70
Deep wallet forensic audit. Traces on-chain history flags suspicious patterns identifies scam links MEV activity and money flow patterns. Returns structured risk score with evidence chain. For security agents doing due diligence.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Blockchain network |
| wallet_address | string | yes | Wallet address for deep forensic analysis |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | array | – | Evidence chain for findings |
| recommendation | string | – | safe_caution_block |
| risk_score | number | – | Overall risk score 0 to 100 |
| scam_indicators | array | – | Suspicious patterns detected |
No examples provided.
What is the Freysa Security MCP server?
Freysa Security is an MCP server listed in the public MCP registry as dev.freysa.economic-agent-369/freysa-intelligence. Security intelligence for AI agents. 27 x402 endpoints: honeypot, forensics, CAPTCHA, preflight. This page covers its hosted endpoint (https://economic-agent-369.freysa.dev/mcp).
Is the Freysa Security MCP server safe to use?
Freysa Security scores 0 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 Freysa Security MCP server expose?
Freysa Security exposes 11 tools: security.trial, captcha.solve, security.score, security.honeypot, security.address, and 6 more. Their descriptions and schemas cost roughly 999 tokens of context every time the server is loaded.
Does the Freysa Security MCP server require authentication?
Its publisher declares no required credentials for Freysa Security. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Freysa Security MCP server still maintained?
Freysa Security has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 27 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.