
TOVREK Current-State Resolver
com.tovrekv0.1.0Updated Oct 6, 2026
Verify DOI metadata before autonomous action; preserve conflicts, provenance, and UNKNOWN.
Overview
AI-generated overview
Lets an assistant verify DOI metadata and preserve conflicts, provenance, and UNKNOWN results before acting.
- What it does
- The server exposes a current-state resolution capability centered on checking DOI metadata before an assistant takes autonomous action. Its stated behavior is to preserve conflicts, provenance, and UNKNOWN outcomes rather than silently resolving them. No tool list is published, so the exact operations are not documented in the supplied material.
- When to use it
- Consider it when a workflow depends on confirming DOI metadata before an automated step, and when it matters that conflicting or unresolved results are surfaced instead of overwritten. It is less useful if you need a broad set of tools or documented operations.
- Requirements
- It is a remote streamable HTTP endpoint at tovrek.com; no packages, environment variables, or headers are declared. The manifest declares no authentication, so no credentials are documented as required.
Before you install
The description is the only supplied detail: no tool list, authentication, or data-handling terms are documented. Before relying on it, confirm what data is sent to the remote endpoint and how conflicts, provenance, and UNKNOWN results are reported.
Installation
In SourceWeft
- Open TOVREK Current-State Resolver in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"current-state-resolver": {
"type": "http",
"url": "https://tovrek.com/mcp"
}
}
}README
This repository has no README.
Tools
0Tool metadata has not been indexed yet.
Version history
1- v0.1.0LatestOct 6, 2026

