example

A remotely hosted MCP server at mcp.example.com, configured for an agent connection.

In plain words
What is it for?
Connecting an agent to whatever tools or data the example server provides; the available functions are not described here.
Why use it?
It lets an agent connect to this external server using a bearer token.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

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/conn-castle/agent-layer/expected-example
Clone the repo
git clone --depth 1 https://github.com/conn-castle/agent-layer

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

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

example 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 yesterday.

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.

internal/sync/testdata/fixture-repo/expected/.mcp.json · 9 lines

What it actually says

{
  "example": {
    "type": "http",
    "url": "https://mcp.example.com?token=${AL_EXAMPLE_TOKEN}",
    "headers": {
      "Authorization": "Bearer ${AL_EXAMPLE_TOKEN}"
    }
  }
}
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. yesterday First seen · 9 lines scan A c445fe3a8182

Subscribe to this mod's changes

example is an MCP server published in the GitHub repository conn-castle/agent-layer (10 stars, last pushed 2d ago), licensed MIT. 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.