MCP inventory and publication readiness
Baseline snapshot: November 4, 2026. Pilot catalog updated November 5. This is a reconciliation of repository catalog metadata, local MCP configuration, deployment inspection and checks performed in this work. It is not a complete network scan or a public service-level claim.
The marketplace lists 51 entries: 13 bundled contracts, eight additional locally configured connectors, and 30 additional standalone MCP implementations verified in the adjacent Daedro platform checkout. The source-only entries identify their executable path in each card. Known aliases of bundled cleaning, model providers and Qdrant are not counted twice. The checked-in manifest is internal/catalog/platform_sources.json. See the live pilot evidence below for the workflows that can be executed. A listing describes a capability; it does not grant access to a personal account or mean its processor is online.
Repository catalog: 13 contracts
| Catalog ID | Category | What is established |
|---|---|---|
| daedro-mcp-hub | Developer tools | Catalog/discovery and local managed control code exist |
| cleaning | Data | Built-in local managed worker; synthetic lifecycle/ownership tests |
| text-stats | Data | Authenticated shared Hub invokes the bundled word-count MCP; live personal/work profile calls passed |
| daedro-control | Developer tools | Contract listing; public hosted acceptance not established |
| daedro-s3 | Data | Pinned read-only MCP container; real authenticated bucket listing passed |
| daedro-chunker | Data | Contract listing; public hosted acceptance not established |
| daedro-data | Data | Contract listing; public hosted acceptance not established |
| daedro-embedding | Search | Contract listing; public hosted acceptance not established |
| daedro-qdrant | Search | Contract listing; public hosted acceptance not established |
| daedro-providers | LLMs | Contract listing; public hosted acceptance not established |
| daedro-voice | Transcription | Shared pilot produced timed transcripts from a real audio file |
| daedro-video | Transcription | Shared pilot produced timed transcripts from a real video file |
| telegram-archive | Social | Archive extraction contract; not the live daedro-telegram connector |
Source: internal/catalog/services.json. That loader explicitly does not probe
deployments. No independent observability MCP was found in this catalog or the
local configured MCP list. Observability is a platform requirement; a missing
listing is not evidence that no monitoring code exists elsewhere.
Local user configuration: 11 connections
| Configured connection | Observed condition | Public/shared blocker |
|---|---|---|
| daedro-s3 | Existing pinned container; real API listing succeeds | Private VM pilot passed vault-backed browsing and two-account/profile API isolation; remaining public release gates apply |
| daedro-text | Local endpoint offline; processor container stopped | Deployment and tenant acceptance |
| daedro-whatsapp-archive | Local endpoint offline; processor container stopped | Deployment and tenant acceptance |
| daedro-voice | Local endpoint available; capabilities and configured provider list respond | Legacy bearer-only connector is unsuitable for sharing; the separate shared pilot enforces signed per-connection ownership |
| daedro-video | Local endpoint available; capabilities respond | Legacy bearer-only connector is unsuitable for sharing; the pilot passed a real video upload, delegated job and scoped result |
| daedro-youtube | Local endpoint offline; API/worker/database stopped | Deployment, provider/session scope and tenant acceptance |
| discord-read | Installed Python MCP; default token file not found | Verify actual credential source; do not claim the user's whole integration lacks credentials |
| adspower-local-api | Configured Node MCP; cached package identified | Pinned runtime, operation permissions and personal browser-profile separation |
| daedro-telegram | Daedro Telegram restricted shared adapter implemented; original personal Compose daemon remains separate | Typed Secret/MFA import and isolated read-only tests passed; deployed dependency probe passed; real owner Telegram API call pending |
| factory | Configured stdio entrypoint | Review lifecycle/admin tools before admitting public users |
| agent-factory | Configured stdio entrypoint | Review lifecycle/admin tools before admitting public users |
Browser-control infrastructure and documentation-only MCPs are excluded from this customer-service inventory. Marketplace publication and local assistant configuration are different registries; their entries must be reconciled by stable service IDs rather than blindly copied or called “ready.”
Earlier pilot evidence (November 4)
The screenshot-confirmed owner pilot completed a synthetic-key fixture through cloud OpenBao. Later direct executor checks completed a real S3 API call and voice/video capabilities using existing local credentials, with output discarded. Those latter checks did not establish vault-backed delivery. The real credential import never passed recovery decryption. No real media transcription or multi-user external-provider isolation was established in this sequence.
For the publication criteria and ownership model, see the shared MCP Hub specification.
Shared pilot evidence (November 5)
The shared S3 pilot supersedes the earlier S3 import failure for the new isolated installation. It stores encrypted state in OpenBao and uses separate Hub, Secret and S3 worker identities.
The media rollout subsequently exercised real audio and video uploads, jobs and results through the cloud Hub. These private CPU workers enforce signed per-connection ownership; the legacy bearer-only processors remain separate.
The Text stats acceptance client completed authenticated word counts through the cloud Hub in both Personal and Work profiles. Responses contained only the word count. Guest and signed-out requests were denied. The browser walkthrough confirmed the 51-entry marketplace and the six review frames in the handbook.
New implementation evidence pending deployed acceptance
- Daedro Dataset Builder keeps catalog ID
datasets. Its bounded adapter executes the real platformdataset_buildMCP and produces JSONL splits plus a manifest from explicitly owner-attested records. Local tests cover real execution, bounds and concurrent input separation. It does not train models. - Daedro Archive Reader keeps ID
offline-ingest. Its actual platform parsers accept submitted text, Markdown, Telegram JSON and WhatsApp text through private temporary assets. Local tests cover all formats, rejection and cleanup. This is separate from the legacytelegram-archiveprocessor contract and does not connect live social accounts. - Daedro Telegram keeps ID
daedro-telegram. The new adapter derives its read-only lifecycle from the existing standalone connector and uses pinned Telethon in a fresh unprivileged child. Typed per-account/profile Secret credentials, MFA approval, separate ticket delivery and in-memory SQLite session import are implemented. Synthetic tests cover isolation, grant revocation, unsafe imports and metadata-IP denial. The original management/messaging daemon and personal session directory are never exposed.
These three subsets are installed on the existing VM. This inventory does not yet claim a verified deployed user flow for them. In particular, no real user Telegram session was imported with MFA or used for a live Telegram API call in this implementation review. Existing stable IDs remain unchanged; public-facing labels use Daedro.
Implemented Daedro expansion — November 5
The public catalog now advertises eight installed workflows, including Daedro Dataset Builder, Daedro Archive Reader and Daedro Telegram. Existing stable IDs (datasets, offline-ingest, daedro-telegram) retain saved-link compatibility. Source provenance still names its original projects.
Dataset and parser code completed real Linux execution, including parallel requests, on the existing VM. Telegram completed installation and private dependency/health probes; a dedicated user's session must still be imported with Authenticator before real Telegram account acceptance can be claimed. The new remote operations are daedro_dataset_build, daedro_ingest_parse, daedro_telegram_connections_list, daedro_telegram_auth_status and daedro_telegram_dialogs_list.