How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

CoreStory mcp_token_management API

The mcp_token_management API from CoreStory — 3 operation(s) for mcp_token_management.

CoreStory mcp_token_management API is one of 47 APIs that CoreStory publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 6 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.26.2.

Requests are made against a single base URL, /.

6 operations 3 paths 8 schemas 1 DELETE2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.26.2
Base URL
https://c2s.corestory.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

CoreStory mcp_token_management API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Enter the Bearer token from Clerk authentication

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

mcp_token_management 6
POST
/api/mcp-tokens
Create a new MCP token
create_mcp_token body → 201default
GET
/api/mcp-tokens
List all MCP tokens
list_mcp_tokens 1 param → 200default
GET
/api/mcp-tokens/{token_id}
Get token details
get_mcp_token 1 param → 200default
PATCH
/api/mcp-tokens/{token_id}
Update token metadata
update_mcp_token 1 param body → 200default
DELETE
/api/mcp-tokens/{token_id}
Revoke a token
delete_mcp_token 1 param → 200default
POST
/api/mcp-tokens/{token_id}/revoke
Revoke a token (alternative endpoint)
revoke_mcp_token 1 param → 200default

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are MCPTokenCreateResponse (14 properties), MCPTokenResponse (12 properties), MCPTokenRevokeResponse (5 properties), MCPTokenListResponse (4 properties). Each schema is shown below with its type and property counts.

MCPTokenUpdateRequest
object
Request to update token metadata.
2 properties
MCPTokenListResponse
object
Response for listing tokens.
4 properties 4 required
MCPTokenCreateResponse
object
Response when creating a new token (includes full token ONCE).
14 properties 9 required
MCPTokenResponse
object
Response for token metadata (without sensitive data).
12 properties 8 required
MCPTokenRevokeResponse
object
Response after revoking a token.
5 properties 4 required
ErrorBody
object
3 properties 2 required
ErrorSchema
object
1 property 1 required
MCPTokenCreateRequest
object
Request to create a new MCP token.
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

corestory-mcp-token-management-api-openapi.yml Raw ↑

Other APIs CoreStory publishes across the network.

CoreStory admin API
CoreStory api_debugging API
CoreStory api_key_management API
CoreStory artifacts API
CoreStory billing API
CoreStory cache API
CoreStory ciu API
CoreStory clerk_authentication API
CoreStory context API
CoreStory conversations API
CoreStory discovery API
CoreStory document_formatters API
Where this information came from

This is an independent, third-party profile of CoreStory mcp_token_management API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.