// MCP SERVER RECORD

Pearlog

Canonical
NPMmcp-server-pearlog
DRisk gradehigh blast radius
Catalogue entry updated 1 days ago
Auth postureNot probedno remote endpoint probed yet
Tools101 Destructive · 4 Write · 5 Read
Worst categoryDestructivegrade tracks the peak, not the average
Capability mix
Destructive 1Write 4Read 5
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 10
delete_ticketDestructiveHighcreate_ticketWriteMediummove_ticketWriteMediumpatch_ticketWriteMediumupdate_ticketWriteMedium
View all 10 tools
get_status_labelsReadLowget_ticketReadLowlist_projectsReadLowlist_ticketsReadLowlist_usersReadLow
These definitions cost 1,313 tokens of context →
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
delete_ticketdeny
create_ticketrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// RUNNING THIS SERVER
DIRECT INSTALL npx -y mcp-server-pearlog

Installed this way, nothing enforces the recommended policy above — calls run exactly as the agent makes them.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.