TMCP HubPartners · Future provider admission
Make your MCP service available without giving away its authority.
TMCP is preparing an admission path for organization-owned, compatible remote HTTPS MCP services. Publication, organization ownership and access grants are separate decisions.
Partner intake not openWhat a provider proposal will require
Service information
- Provider name and responsible owner/contact
- Exact HTTPS MCP endpoint
- Purpose and requested organization/visibility
- Upstream authorization model and accountable owner
TMCP uses standard MCP discovery for tools and schemas; there is no proprietary manifest to author.
Admission and ongoing use
- Submission remains pending and cannot be called
- Sole Root approves after compatible, safe discovery and identity checks
- Separately scoped upstream credentials and user/org grants are mandatory
- Revocation or suspension must remove tool visibility and execution rights
The public catalog does not own your data
TMCP may publish an admitted integration in its platform catalog while an independent business remains the provider and data owner. Granting an organization a catalog entry does not bypass downstream authentication, delegated scopes, user separation or explicit permission checks.
There is no live general provider submission form or provider onboarding queue to send a URL to yet. Do not upload endpoint secrets, OAuth tokens or business credentials through unrelated TMCP forms. Future intake will be announced here after implementation.
Using TMCP now
Start with your personal account.
Verified registration and compatible-client OAuth already exist; private provider routing is a separate upcoming product.