Tugra
NPM · TUGRA
Provenance-aware memory format for AI agents: every claim carries its source, age and boundary.
Available components
Last scanned (35 minutes ago)
Scores higher than 92% of npm servers
Category Memory and Knowledge
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dogrucanemek-alt/tugra). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 56 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 415 tokens (~103/item across 4 items; 4 tools + 0 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 Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 −3
- Stability: pass → 0.80 functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
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 6 Nov 2026 · Analysed npm/tugra@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dogrucanemek-alt/tugra |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dogrucanemek-alt/tugra/.github/workflows/release.yml@refs/tags/v0.1.4 |
| Rekor log index | 2783760886 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b39c6ec3e7e15e29dbbb7f17d2a92b1781b2b634e660daadf378bd25178fea9dc5ca6a4fb918e7301101f75c3ca407f43e8666bc259d853ffd86af75b |
Background: How many MCP packages publish verified provenance →
Dependencies 4 packages
| Packages resolved | 4 |
|---|---|
| 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 →
event_report ~87
Append a telemetry line to akis/YYYY-MM-DD.jsonl. No network.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| agent | string | yes | – |
| blocked | string|null | – | – |
| confidence | number | – | – |
| job | string | yes | – |
| note | string | – | – |
| status | string | yes | – |
| touched | array | – | – |
| world | string | – | – |
No output schema declared.
No examples provided.
fact_propose ~133
Write a draft fact under kasa/_oneriler/ (or quarantine). Secret patterns are rejected before any write; the matching text is never returned. type=boundary is always quarantined. Fake mcp:// sources are not injected.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | authorization agent id |
| body | string | yes | – |
| source | array | – | real evidence; if omitted, kaynak is written empty — mcp:// is not injected |
| title | string | yes | – |
| topic | string | – | – |
| type | string | – | stored as tur; boundary is always quarantined |
| world | string | – | – |
No output schema declared.
No examples provided.
fact_read ~63
Read one fact by uid. Body passes through the presentation layer (injection escaping). Retired facts include superseded_by and the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | authorization agent id (default mcp-readonly@tugra) |
| uid | string | yes | – |
No output schema declared.
No examples provided.
fact_search ~132
Search stored facts. Retired and rotten facts are omitted unless archive is true. Rank: token score, then freshness, then confidence. Boundary facts add a no-claim warning. Authorization required.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | authorization agent id (default mcp-readonly@tugra) |
| archive | boolean | – | include retired and rotten facts; default is the active set |
| limit | integer | – | – |
| query | string | yes | search text |
| scope | string | – | evrensel | kurum | dunya (stored scope values) |
| world | string | – | world id when scope is dunya |
No output schema declared.
No examples provided.
How do I install the Tugra MCP server?
Tugra runs locally as an npm package, launched with npx -y tugra. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tugra
claude mcp add com-tugra-ai-tugra -- npx -y tugra
What is the Tugra MCP server?
Tugra is an MCP server listed in the public MCP registry as com.tugra-ai/tugra. Provenance-aware memory format for AI agents: every claim carries its source, age and boundary. This page covers its npm package (tugra).
Is the Tugra MCP server safe to use?
Tugra scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Tugra MCP server expose?
Tugra exposes 4 tools: fact_search, fact_read, fact_propose, event_report. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.
Is the Tugra MCP server still maintained?
Tugra is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Tugra MCP server under?
Tugra declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Tugra MCP server?
VerifyMCP ran 16 checks on Tugra, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.