Skip to main content
Glama
AntonIXO

vibescience-mcp

by AntonIXO

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VIBESCIENCE_VAULTNoVault path (source of truth)~/vibescience-vault
VIBESCIENCE_EMBEDDINGSNoSet to 'on' to enable local FastEmbed semantic recalloff

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
recallA

CALL THIS FIRST, before proposing any hypothesis (pre-mortem gate).

Returns ranked past hypotheses/experiments. Refuted and inconclusive matches are ranked to the TOP with a one-line reason they failed and the diagnostic delta that killed them — so you never silently re-walk a dead end. Also returns a calibration note if the query touches a diagnostic with a track record. After reading this, propose a NEW hypothesis (or supersede a prior one) with a committed prediction.

create_problemA

Register an open research question / failure mode. Do this once per distinct problem. Use recall first to check it isn't already logged.

get_problemA

Fetch a single problem by id.

list_problemsA

List problems, optionally filtered by status {open|resolved|parked} or tags.

register_diagnosticA

Register a named, fixed, measurable metric. Diagnostics are a DELIBERATE fixed basis — comparability across experiments is what makes the causal map possible. Do this before predicting on a metric.

list_diagnosticsB

List the registered diagnostic basis.

register_interventionC

Register a named, reusable change (e.g. unfreeze-projector). Reused across hypotheses so the causal map can attribute deltas to it.

list_interventionsA

List registered interventions.

propose_hypothesisA

Propose an explanation/intervention for a problem. You MUST commit ≥1 predicted_effect on a REGISTERED diagnostic BEFORE testing — this is rejected otherwise. Committing the prediction up front is what turns this log into a calibration signal. Call recall first. To revise a dead end, pass supersedes rather than deleting it.

start_experimentA

Begin testing a hypothesis. If git_ref is omitted the server reads the current branch@commit from git HEAD. Reference the external W&B/MLflow run — this server stores verdicts, not loss curves.

record_diagnosticsA

Record before/after values for measured diagnostics. Re-recording the same diagnostic overwrites it (idempotent). Observed deltas/directions are derived.

close_experimentA

Finalize: compute observed_effects, prediction_match (per-diagnostic + overall) and the verdict (supports/refutes/inconclusive), then propagate the status to the hypothesis. The verdict is COMPUTED from the primary prediction vs the observation — you cannot assert 'confirmed'. On a positive match it RETURNS a suggestion to commit your git_ref; it never commits for you.

add_paperC

Add an external reference (metadata + key claims). Cite it from hypotheses to ground your rationale.

link_paperB

Link a paper to a problem or hypothesis (adds a cites edge).

causal_mapA

Aggregated intervention → Δdiagnostic subgraph across all experiments in scope: what has ever moved a diagnostic, in which direction, how often, by how much. A mini meta-analysis of your own runs. Scope by problem_id or tag.

calibrationA

Prediction-accuracy report: the fraction of experiments where predicted direction == observed direction. Answers 'where is my intuition miscalibrated?'. Scope by diagnostic, tag, or intervention.

reindexA

Rebuild the disposable SQLite index from the markdown vault (files are truth). Safe to call anytime; produces identical query results.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
guideHow to use this server in the correct scientific order. Read this first.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AntonIXO/vibescience-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server