TimeBase
PYPI · TIMEBASE-MCP · 2 COMPONENTS · SCANNED SEP 20
Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security44
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs a script at install time (build_backend) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1207 tokens (~75/item across 16 items; 15 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the TimeBase MCP server?
TimeBase runs locally as a PyPI package, launched with uvx timebase-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · timebase-mcp
claude mcp add epam-timebase-mcp -- uvx timebase-mcp
{
"mcpServers": {
"epam-timebase-mcp": {
"command": "uvx",
"args": [
"timebase-mcp"
]
}
}
} {
"servers": {
"epam-timebase-mcp": {
"command": "uvx",
"args": [
"timebase-mcp"
]
}
}
} codex mcp add epam-timebase-mcp -- uvx timebase-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"epam-timebase-mcp": {
"type": "local",
"command": [
"uvx",
"timebase-mcp"
],
"enabled": true
}
}
} openclaw mcp add epam-timebase-mcp --command uvx --arg timebase-mcp
mcp_servers:
epam-timebase-mcp:
command: "uvx"
args: ["timebase-mcp"] {
"McpServers": {
"epam-timebase-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"timebase-mcp"
]
}
}
} assistant mcp add epam-timebase-mcp -t stdio -c uvx -a timebase-mcp
{
"mcpServers": {
"epam-timebase-mcp": {
"command": "uvx",
"args": [
"timebase-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.83 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/timebase-mcp@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | unreviewed | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compile_query ~76
Compile TimeBase QQL query. Returns parser-level diagnostics only (not full semantic/logical validation). error_token is the first unexpected token, which may be after the actual root cause.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| query | string | yes | TimeBase QQL query text |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | – |
| error_context | – | – | Short query snippet around parser failure position. |
| error_position | – | – | – |
| error_token | – | – | First unexpected token at parser failure point; may be downstream from root cause. |
| valid | boolean | yes | – |
No examples provided.
execute_query ~64
Execute a TimeBase QQL query
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| limit | integer | – | Maximum number of result rows to include in preview text |
| query | string | yes | TimeBase QQL query text |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_server_configuration ~35
Get the MCP server runtime configuration, some TB server configuration fields may be undefined or have default value until the first connection is established.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| inbound_auth_mode | string | – | – |
| oauth_redirect_uri | – | – | – |
| principal | – | – | – |
| timebase_instances | array | – | – |
| transport | string | yes | – |
| version | string | yes | – |
No examples provided.
get_stream_messages ~105
Get the first or last N messages from a stream
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of messages to retrieve |
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| reverse | boolean | – | If true, read from the end of the stream and return the last N messages |
| space | – | – | Optional stream space to read from; use an empty string for the default space |
| stream_key | string | yes | Stream key to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_stream_schema ~47
Get the schema of a specific stream
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| stream_key | string | yes | Stream key to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| schema_text | string | yes | – |
| stream_key | string | yes | – |
No examples provided.
get_stream_space_time_range ~73
Get the time range of a specific stream space in UTC
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| space | string | yes | Stream space to inspect; use an empty string for the default space |
| stream_key | string | yes | Stream key to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| space | string | yes | – |
| start | – | – | – |
| stream_key | string | yes | – |
No examples provided.
get_stream_symbols ~83
Get the symbols of a specific stream
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | Opaque cursor from a previous call's next_cursor; omit on first page |
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| limit | integer | – | Maximum number of symbols to return in this page |
| stream_key | string | yes | Stream key to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| next_cursor | – | – | – |
| returned_count | integer | – | – |
| stream_key | string | yes | – |
| symbols | array | – | – |
| symbols_changed_since_cursor | boolean | – | – |
No examples provided.
get_stream_time_range ~51
Get the time range of a specific stream in UTC
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| stream_key | string | yes | Stream key to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | – | – |
| start | – | – | – |
| stream_key | string | yes | – |
No examples provided.
get_timebase_activity_detail ~153
Get details for one cursor, loader, connection, or lock. Limited TimeBase server versions support.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Cursor/loader numeric id, connection client id, or lock id/guid/client id. |
| include_instruments | boolean | – | For cursor/loader details, include an instrument page. |
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| instrument_filter | – | – | Optional instrument filter when include_instruments is true. |
| instrument_limit | integer | – | Instrument page size when include_instruments is true. |
| instrument_offset | integer | – | Instrument page offset when include_instruments is true. |
| kind | string | yes | Activity object kind to inspect. |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | object | yes | – |
| instance_key | string | yes | – |
| instruments | – | – | – |
| kind | string | yes | – |
| warnings | array | – | – |
No examples provided.
get_timebase_status ~46
Get TimeBase version, license, and runtime environment. Limited TimeBase server versions support.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| Name | Type | Req | Description |
|---|---|---|---|
| http_url | – | – | – |
| instance_key | string | yes | – |
| license | – | – | – |
| runtime | – | – | – |
| security | – | – | – |
| version | – | – | – |
| warnings | array | – | – |
No examples provided.
list_qql_functions ~91
List QQL function signatures supported by the connected TimeBase server
| Name | Type | Req | Description |
|---|---|---|---|
| function_id | – | – | Optional exact QQL function id to return, e.g. ABS or SMA. Letters, digits and underscores only. When provided, TimeBase filters overloads server-side. |
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| kind | string | – | Function category to return |
| Name | Type | Req | Description |
|---|---|---|---|
| function_count | integer | – | – |
| overload_count | integer | – | – |
| stateful | array | – | – |
| stateless | array | – | – |
No examples provided.
list_stream_spaces ~48
List spaces for a specific TimeBase stream
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| stream_key | string | yes | Stream key to inspect |
| Name | Type | Req | Description |
|---|---|---|---|
| returned_count | integer | – | – |
| spaces | array | – | – |
| stream_key | string | yes | – |
| supports_spaces | boolean | – | – |
No examples provided.
list_streams ~36
List available TimeBase streams with their descriptions
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_timebase_activity ~75
List active cursors, loaders, connections, and locks. Limited TimeBase server versions support.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_key | – | – | TB instance key. Required when multiple TimeBase instances are configured. |
| kind | string | – | Activity collection to return. |
| limit | integer | – | Maximum number of rows to return for each requested collection. |
| Name | Type | Req | Description |
|---|---|---|---|
| connections | array | – | – |
| counts | – | – | – |
| cursors | array | – | – |
| instance_key | string | yes | – |
| loaders | array | – | – |
| locks | array | – | – |
| warnings | array | – | – |
No examples provided.
list_timebase_instances ~17
List configured TimeBase server instances.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the TimeBase MCP server?
TimeBase is an MCP server listed in the public MCP registry as io.github.epam/TimeBase-MCP. Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP. This page covers its PyPI package (timebase-mcp).
Is the TimeBase MCP server safe to use?
TimeBase scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TimeBase MCP server expose?
TimeBase exposes 15 tools: list_timebase_instances, get_server_configuration, get_timebase_status, list_timebase_activity, get_timebase_activity_detail, and 10 more. Their descriptions and schemas cost roughly 1,000 tokens of context every time the server is loaded.
Is the TimeBase MCP server still maintained?
TimeBase is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.