MCP servers › io.github.abeljumanuel › axiom-meridian

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.abeljumanuel/axiom-meridian

Serves only the team rules and lessons learned relevant to a project. Code drifts. Meridian doesn't. — the publisher's description

7 of 8 record checks metRead-only · tools listed 2026-10-23Topic: productivity-and-docs · AI-classifiedversion 0.1.0PythonApache-2.0standard input/output28 tools

Summary

io.github.abeljumanuel/axiom-meridian is a local MCP server listed in the official MCP registry at version 0.1.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 28 tools, 0 resources and 0 prompts.

Record checks

7 of 8 record checks met · 1 does not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: PyPI · listed version current
License: Apache-2.0
Dependencies: no known high or critical advisories
Repository: public
Tools: 28
Described as changing data: 15 of 28 toolsAI-classified
Mainly works on: files and code on the machine it runs on; a databaseAI-classified
Topic: productivity-and-docsAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

15 tools are described as changing something (index_rules_from_markdown, index_lessons_from_markdown, convert_to_atomic_format, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 0.1.0, published 2026-10-15 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-15 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.0 (published 2026-10-15).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

28tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; a database.

15 of 28 tools are described as changing something (creating, editing, deleting, sending or running).

index_rules_from_markdowncreates or changes datadescribed as changing data
“Index rules from a markdown file directly into SQLite.”
3 inputs, 2 required
- filepathstringrequired“Path to the source .md file containing rule blocks.”
- default_scope_idstringrequired“Scope assigned to blocks that don't declare their own **Scope:** field (e.g.”
- modestring“'atomic': parse canonical ## RN-XXX-NNN blocks (the {TECH} segment is optional — plain ## RN-NNN is also accepted) and upsert them directly into rules/rule_his…”
index_lessons_from_markdowncreates or changes datadescribed as changing data
“Index lessons from a markdown file directly into SQLite.”
3 inputs, 2 required
- filepathstringrequired“Path to the source .md file containing lesson blocks.”
- default_scope_idstringrequired“Scope assigned to blocks that don't declare their own **Scope:** field (e.g.”
- modestring“'atomic': parse canonical ## LL-XXX-NNN blocks (the {TECH} segment is optional — plain ## LL-NNN is also accepted) and upsert them directly into lessons/lesson…”
convert_to_atomic_formatcreates or changes datadescribed as changing data
“Convert a legacy markdown file into atomic-format pending_proposals, one per legacy block, with best-effort scope inference from each block's text.”
3 inputs, 3 required
- filepathstringrequired“Path to the legacy (### -style) markdown file to convert.”
- default_scope_idstringrequired“Fallback scope used when scope inference from the block's text doesn't match a known technology keyword.”
- doc_typestringrequired“'rules' or 'lessons' — which legacy parser and destination to use.”
list_pending_proposalsreads or searches
“List pending proposals for human review, optionally filtered by project, type, or status.”
3 inputs
- project_idstring or null“Filter by project/scope id (with or without the 'project-' prefix).”
- typestring or null“Filter by proposal type: 'rule', 'lesson', or 'update'.”
- statusstring or null“Filter by status: 'pending', 'approved', or 'rejected'.”
approve_proposalon 3 other serverscreates or changes datadescribed as changing data
“Approve a pending proposal.”
1 input, 1 required
- proposal_idstringrequired“The pending_proposals id to approve.”
edit_proposalcreates or changes datadescribed as changing data
“Update the proposed_text and/or metadata of a still-pending proposal; its status stays 'pending'.”
3 inputs, 2 required
- proposal_idstringrequired“The pending_proposals id to edit.”
- new_textstringrequired“Replacement proposed_text (private tags are stripped before storage).”
- metadatastring or null“JSON object merged into the proposal's existing metadata.”
reject_proposalon 1 other serverdescribed as changing data
“Reject a pending proposal.”
2 inputs, 1 required
- proposal_idstringrequired“The pending_proposals id to reject.”
- reasonstring or null“Optional human-readable rejection reason.”
promote_rulecreates or changes datadescribed as changing data
“Promote a rule to a more general scope: marks the original as deprecated (in both SQLite and its source .md file) and records a PROMOTED rule_history entry.”
2 inputs, 2 required
- rule_idstringrequired“The RN-* id of the rule to promote.”
- new_scope_idstringrequired“Destination scope to promote the rule into.”
deprecate_rulecreates or changes datadescribed as changing data
“Create a proposal to deprecate a rule or lesson on its own, without changing its scope (unlike promote_rule).”
3 inputs, 2 required
- rule_idstringrequired“The RN-* or LL-* id of the rule/lesson to deprecate.”
- reasonstringrequired“Why this rule/lesson is being deprecated.”
- superseded_bystring or null“Optional RN-*/LL-* id of the active rule/lesson that replaces this one.”
create_projecton 101 other serverscreates or changes datadescribed as changing data
“Create a new project scope and its knowledge base directories: a 'project-<id>' scope under parent_scope, plus knowledge-base/projects/ and lessons/projects/ directories with a placeholder rules .md …”
3 inputs, 1 required
- project_idstringrequired“New project identifier (the tool creates scope 'project-<id>').”
- namestring or null“Human-readable project name; defaults to project_id.”
- parent_scopestring“Existing scope this project inherits from in the scope hierarchy.”
generate_embeddingson 2 other serverscreates or changes datadescribed as changing data
“Generate or update ChromaDB embeddings for active rules/lessons whose embedding_id is still NULL — an incremental backfill, not a full re-embed.”
1 input
- scope_idstring or null“Restrict to one scope; omit to process every scope.”
generate_project_skillscreates or changes datadescribed as changing data
“Generate a Claude Code skill for a project from its resolved rules: writes .claude/skills/meridian/<project_id>/SKILL.md and references/rules.md under project_path, and updates its AGENTS.md.”
2 inputs, 1 required
- project_idstringrequired“Project scope to generate skill files for.”
- project_pathstring or null“Filesystem path to the target project; falls back to MERIDIAN_PROJECT_PATH if omitted.”

Show 16 more tools

query_rulesreads or searches
“Query active rules visible to a project across its full scope hierarchy (most-specific scope first), via plain SQL filtering or — when query_text is set and embeddings exist — semantic search.”
8 inputs, 1 required
- project_idstringrequired“Project id (with or without the 'project-' prefix).”
- categorystring or null“Filter by rule category, e.g.”
- severitystring or null“Filter by severity: 'low' | 'medium' | 'high' | 'critical'.”
- tagsstring or null“Comma-separated tags; matched by exact tag equality, not substring.”
- query_textstring or null“Free-text query.”
- formatstring“Output format: 'json' or 'toon' (compact tabular).”
- detailstring“'summary': metadata only.”
- include_deprecatedboolean“Include deprecated rules.”
query_lessonsreads or searches
“Query active lessons visible to a project across its full scope hierarchy (most-specific scope first), via plain SQL filtering or — when query_text is set and embeddings exist — semantic search.”
7 inputs, 1 required
- project_idstringrequired“Project id (with or without the 'project-' prefix).”
- areastring or null“Filter by area_affected, e.g.”
- tagsstring or null“Comma-separated tags; matched by exact tag equality, not substring.”
- query_textstring or null“Free-text query.”
- formatstring“Output format: 'json' or 'toon' (compact tabular).”
- detailstring“'summary': metadata only.”
- include_deprecatedboolean“Include deprecated lessons.”
get_rule_contextreads or searches
“Return a rule's full text, its complete rule_history, and any lessons linked to it.”
1 input, 1 required
- rule_idstringrequired“The RN-* id of the rule.”
get_rule_timelinereads or searches
“Return a rule's chronological history and linked-lesson summary without loading full text — lighter than get_rule_context.”
1 input, 1 required
- rule_idstringrequired“The RN-* id of the rule.”
get_project_scope_resolutionreads or searches
“Resolve and cache a project's effective scope chain (most-specific first) with each scope's dynamic attributes (ADR-002).”
1 input, 1 required
- project_idstringrequired“Project id (with or without the 'project-' prefix).”
get_server_infoon 26 other serversreads or searches
“Report this running server process's version/commit, and whether the code on disk has changed since this process started — Python doesn't hot-reload, so an editable install that was `git pull`ed with…”
Takes no inputs.
get_rule_audit_logreads or searches
“Return the chronology of rule_history changes for a project or scope, plus any rules currently deprecated in that scope.”
3 inputs
- project_idstring or null“Project id to scope the log to (checked before scope_id).”
- scope_idstring or null“Raw scope id to scope the log to, if project_id is omitted.”
- sincestring or null“ISO-8601 timestamp; only include events at or after this time.”
audit_prreads or searchesdescribed as changing data
“Audit a PR diff against a project's active rules and lessons (detail="full"): persists an audit record (SHA-256 diff hash + a snapshot of the rule versions evaluated) and returns the diff plus rules/…”
2 inputs, 2 required
- pr_diffstringrequired“The PR's unified diff text.”
- project_idstringrequired“Project id whose active rules/lessons to audit against.”
analyze_pr_feedbackreads or searchesdescribed as changing data
“Link PR review feedback to the most recent audit_pr record for the same pr_ref/project_id, returning the rules that applied at that time for the calling LLM to classify each feedback point.”
3 inputs, 3 required
- feedback_textstringrequired“Free-text PR review feedback to classify.”
- pr_refstringrequired“Reference (e.g.”
- project_idstringrequired“Project id the original audit_pr call used.”
check_feature_against_rulesreads or searchesdescribed as changing data
“Check a planned feature description against a project's active rules and lessons (detail="full"); persists a planning_checks record and returns the context for the calling LLM to flag conflicts.”
2 inputs, 2 required
- feature_descriptionstringrequired“Free-text description of the feature being planned.”
- project_idstringrequired“Project id whose active rules/lessons to check against.”
extract_rules_from_transcriptreads or searches
“Return everything the calling LLM needs to extract candidate rules from a transcript: the clean text, the project's scope chain with attributes, existing rules for duplicate detection, and the canoni…”
2 inputs, 2 required
- textstringrequired“Raw transcript text; private tags are stripped automatically.”
- project_idstringrequired“Project id used to resolve scopes and existing rules.”
extract_lessons_from_transcriptreads or searches
“Return everything the calling LLM needs to extract candidate lessons from a transcript: the clean text, the project's scope chain with attributes, existing lessons for duplicate detection, and the ca…”
2 inputs, 2 required
- textstringrequired“Raw transcript text; private tags are stripped automatically.”
- project_idstringrequired“Project id used to resolve scopes and existing lessons.”
create_pending_proposalcreates or changes datadescribed as changing data
“Validate and persist a pending proposal of type 'rule', 'lesson', or 'update' (private tags stripped from proposed_text).”
8 inputs, 3 required
- typestringrequired“Proposal type: 'rule', 'lesson', or 'update'.”
- proposed_textstringrequired“The proposed rule/lesson text (private tags are stripped before storage).”
- suggested_scope_idstringrequired“Scope to attach the proposal to if approved.”
- target_idstring or null“For type='update': the existing RN-*/LL-* id this proposal will replace.”
- target_typestring or null“For type='update': 'rule' or 'lesson'; inferred from target_id's prefix if omitted.”
- suggested_attributesstring or null“JSON array of {"key": ..., "value": ...} dynamic attributes (ADR-002) to attach if approved.”
- source_typestring or null“Provenance type, e.g.”
- source_refstring or null“Provenance reference, e.g.”
get_rule_templatereads or searches
“Return the canonical `## RN-XXX-NNN` atomic block template, its field descriptions, and usage instructions.”
1 input
- project_idstring or null“If given, also returns recommended scope_suggestions for this project.”
get_lesson_templatereads or searches
“Return the canonical `## LL-XXX-NNN` atomic block template, its field descriptions, and usage instructions.”
1 input
- project_idstring or null“If given, also returns recommended scope_suggestions for this project.”
get_transcription_templatereads or searches
“Return the combined rule+lesson template guide and workflow instructions for turning a transcript into pending proposals.”
1 input
- project_idstring or null“If given, also returns recommended scope_suggestions for this project.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 28 tools
Says what it returns: 100% of 28 tools
States limits, defaults or errors: 0% of 28 tools
Says when to use it: 0% of 28 tools
Items covered per tool: 2.0 of 4 on average

Counted from the listing

Parameters with a description: 100% of 72
Tools with a description: 100% of 28
Typical description length: 297 characters

The tool set

Counted from the listing

Tools: 28
Size of the list: about 6,978 tokens for an agent to load (characters ÷ 4)
Naming: 28 of 28 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 28 of 28 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the PyPI package axiom-meridian

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "axiom-meridian": {
      "command": "uvx",
      "args": [
        "axiom-meridian==0.1.0"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "axiom-meridian": {
      "command": "uvx",
      "args": [
        "axiom-meridian==0.1.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "axiom-meridian": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "axiom-meridian==0.1.0"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"axiom-meridian","type":"stdio","command":"uvx","args":["axiom-meridian==0.1.0"]}'

Claude Code

claude mcp add --transport stdio axiom-meridian -- uvx axiom-meridian==0.1.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- uvx axiom-meridian==0.1.0

Optional settings the entry also lists (left out above): KNOWLEDGE_BASE_PATH, MERIDIAN_ACCESS_LEVEL.
This runs the publisher's code on your machine (uvx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.1.0
Latest stable: 0.1.0
Status: current
Withdrawn: no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha256-da2ee54972cc253ae…
License: Apache-2.0

Source: the package registry · 2026-10-23.

Usage

Downloads: 0 in the last month

Source: pypistats.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.1.0 on PyPI	Exists and can be installed	matches	PyPI · 2026-10-23
Repository github.com/abeljumanuel/axiom-meridian-project	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.abeljumanuel
GitHub owner: a personal account (abeljumanuel)

Repository: github.com/abeljumanuel/axiom-meridian-project
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 8 record checks met · 1 does not apply

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
MetPackage names its licence with a standard (SPDX) identifierApache-2.0
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.abeljumanuel/axiom-meridian

Answered from the data above

Is io.github.abeljumanuel/axiom-meridian safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 15 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.abeljumanuel/axiom-meridian been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.abeljumanuel/axiom-meridian do?

It lists 28 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.abeljumanuel/axiom-meridian change or delete data?

15 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.abeljumanuel/axiom-meridian publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.1.0, the latest stable release on PyPI.

Where is the source code of io.github.abeljumanuel/axiom-meridian?

In github.com/abeljumanuel/axiom-meridian-project, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.usekaneo/kaneoalso has tools that creates or changes data, reads or searchescompare with this one
io.github.54yyyu/zotero-mcpZotero MCPalso has tools that creates or changes data, reads or searchescompare with this one
io.github.haris-musa/excel-mcp-serverExcel MCP Serveralso has tools that creates or changes data, reads or searchescompare with this one
io.github.iwe-org/iweIWEalso has tools that creates or changes data, reads or searchescompare with this one
io.github.silverstein/minutesalso has tools that creates or changes data, reads or searchescompare with this one
io.github.Softeria/ms-365-mcp-serverMicrosoft 365 MCP Serveralso has tools that creates or changes data, reads or searchescompare with this one

Active servers whose topic is also “productivity-and-docs” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
2,648 msConnected after 0 redirects.
Read the inventory: 28 tools, 0 resources, 0 prompts.
5,325 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

productivity-and-docs

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

The website listed in the registry is a code-hosting, package or marketplace page, not the product's own site.

Programming language

Python

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

logging, prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

pypi

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sha256)

package registry · 2026-10-23

Signature / provenance

does not apply

PyPI publishes no registry signature or attestation equivalent to npm dist.signatures

Dependency advisories

none known

OSV.dev · 2026-10-23

Popularity

0 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.abeljumanuel/axiom-meridian: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.abeljumanuel/axiom-meridian

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.abeljumanuel/axiom-meridian)](https://protocolprobe.com/mcp/servers/io.github.abeljumanuel/axiom-meridian)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology