Freysa Security

dev.freysa.economic-agent-369Published by economic-agent-369.freysa.devOfficial publisherv1.1.1Updated Oct 27, 2026

Security intelligence for AI agents. 27 x402 endpoints: honeypot, forensics, CAPTCHA, preflight.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringAI & ML

Overview

AI-generated overview

Remote security-intelligence endpoint for AI agents, offering 27 x402 endpoints covering honeypot, forensics, CAPTCHA and preflight checks.

What you can do
  • Honeypot services for detecting or trapping malicious activity
  • Forensics endpoints for investigating security incidents
  • CAPTCHA-related endpoints
  • Preflight checks, presumably to vet actions or requests before they run
  • All of it is reached through a single remote endpoint with 27 x402-style endpoints; no individual tools are documented.
When to use it
Worth considering when an agent needs security checks built in, such as screening requests before acting, running forensics on suspicious activity, or adding CAPTCHA and honeypot capabilities to an agent workflow.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. The x402 endpoints likely involve payment-style access, so a compatible client or wallet may be needed, though this is not stated.
Before you install
The manifest declares no authentication, yet the endpoints are described as x402, which typically means per-call payments; confirm how access and billing work before use. No tool list, README or instructions are provided, so behavior and data handling are unverified. Security-related requests may send sensitive data to a third-party service.

Installation

In SourceWeft

  1. Open Freysa Security in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.freysa.economic-agent-369%2Ffreysa-intelligence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "freysa-security": {
      "type": "http",
      "url": "https://economic-agent-369.freysa.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.