Retio Pagemap MCP Server

retio-pagemap PyPI v1.1.1

Published by retio-ai — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
B
83/100
Last scanned
Trust
B · 83/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
B Why this grade 100 − 17.5 = 83/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−15.4 Obfuscated / encoded payload in server code MTC-SRC-004 injection
−2.1 Package has no source repository MTC-SUP-011 supply-chain

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind the deduction.

Findings 7

high Reads a sensitive credential path or dumps the environment (tests/test_agent_friendly_errors.py)MTC-SRC-006

In the server's implementation (`tests/test_agent_friendly_errors.py:91`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: id_rsa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_agent_friendly_errors.py

high Reads a sensitive credential path or dumps the environment (tests/test_resource_guards.py)MTC-SRC-006

In the server's implementation (`tests/test_resource_guards.py:251`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ~/.ssh

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_resource_guards.py

high Reads a sensitive credential path or dumps the environment (tests/test_sanitizer.py)MTC-SRC-006

In the server's implementation (`tests/test_sanitizer.py:130`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ~/.ssh

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_sanitizer.py

high Reads a sensitive credential path or dumps the environment (tests/test_server_security.py)MTC-SRC-006

In the server's implementation (`tests/test_server_security.py:45`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: id_rsa

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_server_security.py

high Obfuscated / encoded payload in server code (tests/test_take_screenshot.py)MTC-SRC-004

In the server's implementation (`tests/test_take_screenshot.py:42`): Decoding an encoded blob and executing it is how malicious logic is hidden from human review of the source. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: \x00\x00\x00\x01\x00\x00\x00\x01\x08\x06\x00\x00\x00\x1f\x15\xc4\x89

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_take_screenshot.py

medium Dynamic module load from a non-literal (src/pagemap/server/session_manager.py)MTC-SRC-005

In the server's implementation (`src/pagemap/server/session_manager.py:11`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import (acyclic)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/pagemap/server/session_manager.py

low Package has no source repositoryMTC-SUP-011

"retio-pagemap" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package retio-pagemap

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.1 latest B 83/100 7 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 83/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/retio-pagemap/badge.svg)](https://mcptrustchecker.com/registry/retio-pagemap)
HTML
<a href="https://mcptrustchecker.com/registry/retio-pagemap"><img src="https://mcptrustchecker.com/registry/retio-pagemap/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/retio-pagemap/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan retio-pagemap --online --registry pypi

Use the free API → How scoring works

More in Browser Automation