Atinamos Evidence vs MCP Server Scf

In-depth architectural comparison of the Atinamos Evidence and MCP Server Scf MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

A

Choose Atinamos Evidence when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Atinamos Evidence Details

Choose MCP Server Scf when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore MCP Server Scf Details

Feature & Specification Comparison

Specification	A Atinamos Evidence Developer Tools	MCP Server Scf Developer Tools
Summary	Read-only verification evidence for paid machine services and buyer policy checks.	MCP server for the SCF Controls Platform — 72 tools for controls, evidence, risk, and TPRM.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "atinamos-evidence": {
      "command": "npx",
      "args": [
        "-y",
        "atinamos-evidence"
      ]
    }
  }
}

{
  "mcpServers": {
    "mcp-server-scf": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

Related MCP Server Comparisons