acme-api

acme-api is an MCP server for Claude Code, Codex, Cursor, Gemini CLI, OpenCode from harnessprotocol/harness-kit. Its token cost is not measured, scanned A, original, Apache-2.0.

A configured connection to a remote MCP server, which is a service that lets an agent call external tools or data sources. The example points to an Acme API server and includes an authorization token setting.

In plain words
What is it for?
Use it to configure access to the Acme API through an MCP-compatible agent setup.
Why use it?
It provides the connection details needed for an agent to communicate with that external service.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

One of 2 entries in .mcp.json — they are configured in one file and arrive together.

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add mcp/harnessprotocol/harness-kit/mixed-project-acme-api
Clone the repo
git clone --depth 1 https://github.com/harnessprotocol/harness-kit

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for acme-api

README.md
[![agentmods](https://agentmods.dev/badge/mcp/harnessprotocol/harness-kit/mixed-project-acme-api.svg)](https://agentmods.dev/mcp/harnessprotocol/harness-kit/mixed-project-acme-api)
Your own site
<a href="https://agentmods.dev/mcp/harnessprotocol/harness-kit/mixed-project-acme-api"><img src="https://agentmods.dev/badge/mcp/harnessprotocol/harness-kit/mixed-project-acme-api.svg" alt="Measured on agentmods" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

acme-api scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/core/fixtures/import/mixed-project/.mcp.json · 9 lines

What it actually says

{
  "acme-api": {
    "type": "http",
    "url": "https://api.acme.example.com/mcp",
    "headers": {
      "Authorization": "Bearer sk-FAKE"
    }
  }
}
Same file

What else .mcp.json configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 9 lines scan A 27c55598e917

Subscribe to this mod's changes

acme-api is an MCP server published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed 4d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.