com.picaos/mcp

Name: com.picaos/mcp
Author: com.picaos

MCPattested

v2.0.3com.picaosUnknownUpdated 11mo agonpm GitHub

A Model Context Protocol Server for Pica

A Model Context Protocol (MCP) server that integrates with Pica, enabling seamless interaction with various third-party services through a standardized interface. This server provides direct access to platform integrations, actions, execution capabilities, and robust code generation capabilities. listpicaintegrations - List all available platforms and your active connections…

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

11mo agoLast update

Package

Authorcom.picaos

LicenseUnknown

Version2.0.3

Sourcemcp-registry

npm@picahq/mcp

GitHubpicahq/mcp

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

✓npm Trusted Publishing (Sigstore)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 40bb184

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface4 tools · 1 privileged

Security scan✓ Cleanv2.1.3 · 3mo agoHow well does this scan work?

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · 1 privileged

Statically extracted from the published packagev2.1.3 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_pica_integrationsNo description published

This tool published no description. Forge does not invent one.

search_pica_platform_actionsNo description published

This tool published no description. Forge does not invent one.

get_pica_action_knowledgeNo description published

This tool published no description. Forge does not invent one.

execute_pica_actionprivilegedNo description published

This tool published no description. Forge does not invent one.

0 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Keywords

mcp

Alternatives

Comparing tool surfaces…

com.picaos/mcp

Tools

Tools exposed

No dependency coverage