v0.9.1MCP 2026-07-2876 tools
Use PlatPhorm MCP
A task-first guide for humans and agents. Start with intent, inspect a small ranked result, then call one canonical tool with schema-valid arguments.
1
Describe the task
Call the public recommender with a short plain-English intent.
2
Inspect the match
Check owner, status, authorization, reasons, and the exact input schema.
3
Call one tool
Use only the returned canonical name in a JSON-RPC tools/call envelope.
Fast agent request
Recommendations are deterministic, bounded, cacheable, and include a ready invocation structure.
GET /api/v1/model/recommend-tools?task=check%20site%20health&limit=5
POST /mcp
{"jsonrpc":"2.0","id":"call-1","method":"tools/call","params":{"name":"<canonical-name>","arguments":{}}}Reference library
Searchable, paginated human and machine surfaces. Public pages never contain credentials.
Showing 1-12 of 18 references
MCP endpoint
POST/mcpJSON-RPC initialize, discovery, listing, reading, prompt retrieval, and tool execution.
Tool recommender
GET or POST/api/v1/model/recommend-toolsTurn plain-English intent into at most 20 ranked, schema-bearing tool recommendations.
Agent tool-calling skill
Markdown/skills/platphorm-mcpCompact instructions an agent can load before selecting and calling tools.
Tool catalog
UI/toolsSearch paginated local handlers and inspect a bounded source-owned network preview.
Structured API docs
JSON/api/docsMachine-readable endpoint, tool, resource, and prompt documentation.
OpenAPI 3.1
YAML/openapi.yamlREST surface contract and PLATPHORM_API_KEY security scheme.
LLM summary
Text/llms.txtConcise service purpose, calling guidance, policies, and machine links.
Full LLM reference
Text/llms-full.txtExpanded capability and schema reference generated from real registry state.
LLM index
JSON/llms-index.jsonStructured live counts, capabilities, client configuration, and discovery links.
MCP discovery
JSON/.well-known/mcp.jsonTransport, protocol, capability counts, and integration metadata.
Agent discovery
JSON/.well-known/agents.jsonSecret-safe client and agent integration profiles.
Trust policy
JSON/.well-known/trust.jsonPublic/protected boundary, trusted domains, and data exposure rules.
Client configuration
Use Streamable HTTP. The endpoint is stateless; do not embed a shared key in public configuration.
{
"mcpServers": {
"platphormnews": {
"url": "https://mcp.platphormnews.com/mcp"
}
}
}Preferred protocol version: 2026-07-28
Authorization boundary
Discovery and public-safe reads are open. Mutations, delegation, proxying, sync, tests, reports, and administration require PLATPHORM_API_KEY supplied from a server-side secret store.