Tested authorization policy pack — Atom
Pay-per-call MCP service that checks an authorization policy pack and returns a verdict
The server answered 2 hours ago with a sign-in request for an API key (HTTP 401), so we could not list its tools.
- Platforms
- API, Web
- Runs
- Remotely
- Access
- Needs sign-in (API key)
- Version
- 0.1.0
- Listing updated
- 1 day ago
Similar MCP servers
About Tested authorization policy pack — Atom
Tested authorization policy pack — Atom is an MCP server for security. It runs as a hosted remote server, so there is nothing to install locally.
This is one atom on Conduit Atoms, a catalogue of small services that each return a single bounded artifact per API call. It is exposed as a remote streamable-http MCP endpoint at atoms.pipavia.com, so an MCP client can call it directly with a key issued for this atom.
The catalogue describes sibling atoms as taking a declared evidence manifest and returning a deterministic verdict (for example SOUND, NOT_SOUND or INSUFFICIENT_EVIDENCE) with per-check evidence. This atom's own manifest format, sections and checks are not spelled out in the available material, so refer to its documentation link on the Conduit Atoms page before integrating.
Access works through a gateway: sign up with an email, issue a key for the atom, and call it over the API or MCP. Each atom is metered at its own posted rate. The source repository says atoms are meant to be released one by one and that nothing in the repo was deployed or live at the time of its README.
Install
Run in a terminal
claude mcp add --transport http atom-tested-authorization-policy-pack https://atoms.pipavia.com/mcp/tested-authorization-policy-packAdd to Settings → Connectors → Add custom connector
https://atoms.pipavia.com/mcp/tested-authorization-policy-packAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"atom-tested-authorization-policy-pack": {
"url": "https://atoms.pipavia.com/mcp/tested-authorization-policy-pack"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"atom-tested-authorization-policy-pack": {
"type": "http",
"url": "https://atoms.pipavia.com/mcp/tested-authorization-policy-pack"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"atom-tested-authorization-policy-pack": {
"serverUrl": "https://atoms.pipavia.com/mcp/tested-authorization-policy-pack"
}
}
}Add to Grok Bot desktop app → Connect apps → Add a custom connector
https://atoms.pipavia.com/mcp/tested-authorization-policy-packEnter a Name (for example "Tested authorization policy pack — Atom"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin. When we checked, this server asked for an API key. Add it under HTTP headers, using the header name from the server's docs.
Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"atom-tested-authorization-policy-pack": {
"type": "http",
"url": "https://atoms.pipavia.com/mcp/tested-authorization-policy-pack"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Remote MCP endpoint
- Served over streamable-http at atoms.pipavia.com/mcp/tested-authorization-policy-pack, with no local package to install.
- Per-call delivery
- Each call returns one bounded artifact, billed per unit delivered rather than by subscription.
- Key-gated gateway
- A single gateway key from an email signup can be issued per atom and used across the catalogue.
- API and MCP access
- The same atom can be called over a REST-style API or through an MCP client.
- Machine-readable catalogue
- The Conduit Atoms catalogue publishes a machine-readable twin at /api.json for discovery.
Good for
- Reviewing an authorization policy pack from inside an MCP-enabled agent workflow
- Adding a pay-per-call policy check to a CI or release pipeline
- Getting a repeatable verdict artifact for security or compliance review
- Experimenting with Conduit Atoms using one gateway key across several atoms
Pricing
Pricing unknown
Metered per call at a posted per-atom rate; this atom's rate is not shown
Prices change. Check atoms.pipavia.com before you buy.
Tested authorization policy pack — Atom FAQ
How do I connect to it?
Use the remote streamable-http MCP URL https://atoms.pipavia.com/mcp/tested-authorization-policy-pack with a key issued for this atom.
How is it priced?
Atoms are metered per unit delivered at each atom's posted rate. Some atoms are listed as free during a trial with the rate pending; this atom's rate is not shown in the available material.
Do I need to install anything?
No package is listed in the registry entry; it is a hosted remote endpoint.
Who makes it?
It is part of the atom-services repository by Nrupal Akolkar, billed under AIMLDS via Conduit.
How do I add Tested authorization policy pack — Atom to Claude Code?
Run this command in your terminal: claude mcp add --transport http atom-tested-authorization-policy-pack https://atoms.pipavia.com/mcp/tested-authorization-policy-pack
What are the best alternatives to Tested authorization policy pack — Atom?
The closest alternatives to Tested authorization policy pack — Atom are Zero trust architecture design pack — Atom, Technical documentation pack — Atom, Testing strategy regression pack — Atom, Sourced podcast episode production — Atom and Release pack changelog seal rollback — Atom.
Where this comes from
- Description: written from the project's README, the project's website and its MCP Registry entry.
- Status: checked automatically by AIPoweredBot on 19 November 2026.
- Install steps: from the official MCP Registry entry.