EP AgentIAM

io.github.achilliesbotPublished by GitHub account achilliesbotv1.0.0Updated Oct 24, 2026

AI agent execution safety via x402 micropayments: risk scoring, integrity, memory checks

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP endpoint that offers AI agent execution safety checks, including risk scoring, integrity and memory checks, tied to x402 micropayments.

What you can do
Provides AI agent execution safety checks, described as risk scoring, integrity checks and memory checks, for agent runs. The registry description links these checks to x402 micropayments. No tool list is published, so the exact operations an assistant can call are not documented. It is reached as a hosted remote endpoint rather than a local package.
When to use it
Consider it when you want an assistant or agent workflow to run safety-oriented checks, such as risk scoring or integrity and memory checks, before or during agent execution. Because no tools are documented, confirm the actual capabilities before relying on it.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. No authentication, environment variables or headers are declared, and no local runtime or package is needed.
Before you install
The description mentions x402 micropayments, which typically involve paying for requests; check costs and payment handling before use. No tools, authentication or data-handling details are published, so what data is sent to the provider and what actions the server can take are unclear.

Installation

In SourceWeft

  1. Open EP AgentIAM 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/io.github.achilliesbot%2Fep-agentiam/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": {
    "ep-agentiam": {
      "type": "http",
      "url": "https://achillesalpha.onrender.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.