Other · Remote MCP server
What Matters
Your personal action-item list - what you owe and what you're owed. AI proposes; you approve.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.blackdogranch/what-matters- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-12
- Updated
- 2026-08-12
- Publisher
- com.blackdogranch
- Namespace
- Namespace verified by the MCP Registry via the domain blackdogranch.com · how
- Website
- matters.blackdogranch.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://matters.blackdogranch.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- what-matters 1.0.0 · protocol 2025-06-18
- Tools discovered
- 6:
get_document,put_proposal,manage_rule,manage_focus,add_item,complete_item - Checked on
- 2026-10-05
How to connect What Matters
What Matters is a remote MCP server: there is nothing to install. Its endpoint is https://matters.blackdogranch.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| WhaleScope MCPBinance Futures market intelligence: funding, OI, order book, klines, cross-exchange comparison. | Remote · HTTPLive check: ✗ no handshake |
| WhalesyncBuild and manage Whalesync syncs: connect apps, map tables and fields, monitor and fix issues. | Remote · HTTPLive check: sign-in required |
| What a Plan! - MCP ServerDescubre eventos en España: filtra por texto, categoría, ubicación, precio y fecha. 38 categorías. | Remote · HTTPLive check: ✓ handshake |
| What Led ToLiving, source-backed timelines of long-running events, with a quote and source per entry. | Remote · HTTPLive check: ✓ handshake |
| What's AllowedMerged agent permission rules: which settings file wins, and which rules your client ignores. | Local · stdio |
| What's InheritedWhat a checkout tells your agent to do: instruction files, hooks, declared MCP servers. | Local · stdio |
| What's LoadedWhat fills your agent's context window before a session starts: skill descriptions, memory files. | Local · stdio |
| What's RunningLive OS ground truth for agents: running agent sessions, listening ports, daemons, system load. | Local · stdio |