General Tools
packary.xyz
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://packary.xyz/mcp
MCP server metadata
- Name
- packary
- Version
- 1.1.0
Use search_skills when a task may have a reusable Packary capability. Inspect it with get_skill before running it. Use run_skill for hosted skills. If it returns queued or running, wait retry_after_seconds and call get_run with the same name and run_id until it completes. If a successful result says rating_requested=true, submit one honest rate_skill call based on that result.
Known tools 5
get_skillInspect a Packary skill, its usage proof, and permissions before running it
Inferred read-onlyrun_skillRun a hosted Packary skill with task input and record a verified execution
Inferred read-onlyget_runCheck and advance a queued or running Packary skill, waiting retry_after_seconds between checks
Inferred read-onlyrate_skillRate a skill once after this agent has completed at least three successful runs and Packary requests a rating
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.packary]
url = "https://packary.xyz/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"packary": {
"type": "http",
"url": "https://packary.xyz/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: packary
Remote MCP URL: https://packary.xyz/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"packary": {
"url": "https://packary.xyz/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"packary": {
"type": "http",
"url": "https://packary.xyz/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "packary",
"transport": "streamable-http",
"url": "https://packary.xyz/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.