# Runlog MCP server

Verified registry of third-party-system knowledge — the external-dependency layer for agent memory.

## Links
- Registry page: https://www.getdrio.com/mcp/org-runlog-runlog
- Repository: https://github.com/runlog-org/runlog
- Website: https://runlog.org

## Install
- Endpoint: https://api.runlog.org/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (required; secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://api.runlog.org/mcp
- Header: Authorization

## Tools
- runlog_search - Find knowledge entries relevant to an external-dependency problem.

All parameters except *query* are optional. Authentication is required
(Authorization: Bearer <key>). Endpoint: https://api.runlog.org/mcp
- runlog_submit - Contribute a new knowledge entry about an external-dependency behaviour.

The entry is validated against schema/entry.schema.yaml, checked for
scope (public-only domain tags) and contamination (credentials, PII), then
embedded and stored. When ``verification_signature`` is supplied the
bundle is cryptographically verified against the calling key's registered
Ed25519 pubkey ([F24] prereq #2); unsigned submits still land at
status='unverified' as before. Endpoint: https://api.runlog.org/mcp
- runlog_report - Report whether a retrieved entry succeeded or failed in the caller's context.

Outcome telemetry drives the stub confidence update (v0.1) and will feed
the full decay/correlation engine in Phase 3. Endpoint: https://api.runlog.org/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: org.runlog
- Version: 0.1.0
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Apr 30, 2026
- Source: https://registry.modelcontextprotocol.io