Research Deposition MCP
Related Servers
Alternatives to Research Deposition MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceEnables deterministic, harness-neutral research workflows by unifying research object identity, evidence receipts, claim-evidence graphs, and append-only decision logs, along with specialized scholarly skills for literature analysis, reproducibility audits, and multi-agent review.181-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate DSpace repositories through a typed interface, including SAF package building, metadata editing, scientometric harvesting, open-access PDF downloads, and repository administration.MIT
- AlicenseAqualityCmaintenanceEnables searching HAL and preparing, validating, and submitting publication deposits via SWORD, with dry-run validation and explicit submission control.14MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read a community's FAIR Implementation Profile and retrieve its agreed identifiers, repositories, formats, vocabularies, licences and provenance choices, then run deterministic pass/fail compliance checks on folders or Zenodo records and crosswalk practices between communities. Community gaps are reported as gaps so the agent asks the user rather than inventing a default.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables cooperating AI agents to manage versioned files and JSON key-value state, record tool-call history, and publish changes atomically after dependency validation.1MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to assemble tamper-evident, locally stored evidence bundles that capture Git state, command results, and file hashes, then verify freshness and export shareable reports.241MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct responsibility in the deposition lifecycle—status, validation, manifest building, package building, draft creation, retrieval, update, file upload, review, and publication. Even the two validation-related tools (validate_deposition and create_draft) are separated by action, and descriptions clarify their boundaries.
Most tools follow a consistent verb_noun pattern (validate_deposition, build_file_manifest, create_draft, upload_file, publish_draft), but a few use noun-first names (deposition_status, publication_review) that break the pattern slightly. This is a minor deviation and does not impede understanding.
With 10 tools covering the complete deposition workflow, the count is well within the ideal 3-15 range. Each tool serves a necessary, non-redundant role in the pipeline, and none feel extraneous.
The tool set covers the full deposition lifecycle: validation, manifest/package building, draft creation/retrieval/update, file upload, review, and publication. There are no obvious gaps for the stated purpose—only minor absent operations like listing or deleting drafts, which are not critical to the core workflow.