_ registry / mcp + a2a streamable-http

moses-mcp

https://mcp.mos2es.org

Registry code: cfc5a9d0af66353f

api record
endpoint
https://mcp.mos2es.org/mcp
door code
2c1df6f8d3e6b480
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 27 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 27 tools
27 never probed 0 of 27 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_operator_system_decomposition unknown never probed

    Two-way ANOVA-style decomposition partitioning metric variance into operator effect, system effect, and operator×system interaction. Computed from raw observations grouped by platform. Shows whether operator capability or system choice drives performance.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "operator_id": {
      "type": "string",
      "description": "Optional: filter to a single operator's decomposition"
    }
  }
}
    arguments 9 lines
  • get_lineage_chain unknown never probed

    Get the full lineage chain for an operator: STATE_A → BI_ACTION → AAI_TRANSFORMATION → BI_REDIRECTION → AAI_EXTENSION → COMMITTED_STATE → OUTCOME. Built from raw lineage and outcome data.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id"
  ],
  "properties": {
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_046)"
    }
  }
}
    arguments 12 lines
  • get_lineage_summary unknown never probed

    Get lineage summary across the cohort — total lineages, workflow breakdown, average micro-eval metrics, outcomes linked. Computed from raw lineage data.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_outcome_correlation unknown never probed

    Correlate micro-eval metrics with outcome quality scores and cycle times through lineage. Computed via Pearson r from raw lineage + outcome data. Results labeled ASSOCIATION with evidence grade OBSERVATIONAL, never CAUSATION.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_org_topology unknown never probed

    Organization-level AI topology map — team-level metric distributions, median canonical metrics per team, capability concentration (Gini coefficient), platform adoption, single-point-of-failure detection, cross-team complementarity. Computed from raw measurements.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_operator_similarity unknown never probed

    Nearest-neighbor operator search using percentile-rank normalization and Euclidean distance across canon metrics. Computed from raw measurements. Returns comparable operators/cohorts, NOT personality matching.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id"
  ],
  "properties": {
    "n_neighbors": {
      "type": "integer",
      "default": 5,
      "description": "Number of nearest neighbors to return"
    },
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001)"
    }
  }
}
    arguments 17 lines
  • get_pilot_status unknown never probed

    Get pilot status overview — cohort size, observation count, date range, data quality, active interventions. Computed from raw observations. Data is from a 50-operator synthetic pilot (labeled synthetic).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_operator_profile unknown never probed

    Get operator profile — operator details, measurements (8 canon metrics computed from raw token observations with values, percentiles, status), and benchmark availability. Operator IDs are pseudonymous (e.g., op_001). Data is synthetic.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id"
  ],
  "properties": {
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001, op_003, op_034)"
    }
  }
}
    arguments 12 lines
  • get_cohort_distribution unknown never probed

    Get cohort metric distribution — min, p10, p25, median, p75, p90, max, mean, std, and outliers for a given metric across the 50-operator cohort. Computed from raw observations.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "metric": {
      "type": "string",
      "default": "leverage",
      "description": "Metric: leverage, yield, token_snr, log_leverage, construction, velocity, scale_v, efficiency"
    }
  }
}
    arguments 10 lines
  • verify_change unknown never probed

    Verify a measured change after intervention — pre/post comparison. Results are ASSOCIATION, never CAUSATION.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id"
  ],
  "properties": {
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001, op_003, op_034)"
    },
    "intervention_id": {
      "type": "string",
      "description": "Intervention ID (e.g., intv_001)"
    }
  }
}
    arguments 16 lines
  • attach_outcome_dataset unknown never probed

    Attach external outcome dataset for join analysis. Outcome joins are ASSOCIATION, never CAUSATION. REQUIRES AUTHORIZATION.

    mcp-tool

    {
  "type": "object",
  "required": [
    "source"
  ],
  "properties": {
    "format": {
      "type": "string",
      "description": "Data format (e.g., 'json', 'csv', 'jsonl')"
    },
    "source": {
      "type": "string",
      "description": "External outcome data source name (e.g., 'jira', 'github', 'linear')"
    }
  }
}
    arguments 16 lines
  • get_composite_score unknown never probed

    Get developmental composite score (0-100) for an operator. Computed from 4 canon metrics normalized via reference percentiles. Labeled DEVELOPMENTAL, not PERSONNEL. Note: composite score is a developmental aggregation, not a canon metric. Weighted: leverage 30%, yield 30%, token_snr 20%, construction 20%. Data is synthetic.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id"
  ],
  "properties": {
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001, op_003, op_034)"
    }
  }
}
    arguments 12 lines
  • get_composite_score_summary unknown never probed

    Get cohort composite score summary — count, min, max, median, mean, Q1, Q3. Computed from per-operator scores. No individual rankings exposed. Label is DEVELOPMENTAL.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_diagnostics unknown never probed

    Get operator diagnostics — pattern detections and diagnoses computed from divergence analysis. All diagnoses are HYPOTHESIS, never fact.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id"
  ],
  "properties": {
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001, op_003, op_034)"
    }
  }
}
    arguments 12 lines
  • get_data_quality unknown never probed

    Get data quality summary — completeness, coverage, validity across the cohort. Computed from raw observations.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • find_usage_operation_divergence unknown never probed

    Find operators with usage-operation divergence. Computes usage percentile from raw token totals and compares to yield percentile. Returns all 50 operators with divergence class (LOW_USAGE_HIGH_OPERATION, HIGH_USAGE_LOW_OPERATION, etc.).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_workflow_fit unknown never probed

    Get workflow fit analysis — operator/workflow fit scores across workflow stages.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_intervention_status unknown never probed

    Get all interventions — 12 active interventions with operator IDs, catalog IDs, reason patterns, target metrics, start dates, followup periods, and synthetic outcomes.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_pilot_options unknown never probed

    List available pilot options — 8 canon metrics, 15 eval families, 13 benchmark classes, 5 intervention types.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • validate_pilot_configuration unknown never probed

    Validate a pilot configuration before deployment. Returns valid status with warnings and errors.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "configuration": {
      "type": "object",
      "description": "Pilot configuration object (JSON) — see list_pilot_options for available metrics, eval families, and benchmark classes"
    }
  }
}
    arguments 9 lines
  • compare_operator_to_reference unknown never probed

    Compare an operator to a reference population. Returns benchmark selection, comparison group, and metric comparison. Computed from raw metrics and reference field.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id"
  ],
  "properties": {
    "reference": {
      "type": "string",
      "description": "Reference population name"
    },
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001, op_003, op_034)"
    }
  }
}
    arguments 16 lines
  • get_executive_dashboard unknown never probed

    Get executive dashboard info — the dashboard is a self-contained HTML file generated by the CLI (enterprise export dashboard --output file.html).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • create_pilot_configuration unknown never probed

    Generate a saveable pilot configuration JSON from parameters. This is a READ-ONLY tool that assembles a configuration object from the supplied arguments — it does not write to any persistent store. The returned configuration contains cohort_size, duration_days, and the selected metrics list. Use list_pilot_options first to discover available metric IDs, eval families, and benchmark classes, then pass the desired metrics here. The returned configuration can be passed to validate_pilot_configuration for pre-deployment checks, or to create_experiment to pair it with a hypothesis. When to use: when you are scoping a new pilot engagement and need a structured configuration object that captures cohort size, observation window, and metric selection. When NOT to use: when you need to validate an existing configuration (use validate_pilot_configuration), or when you need to create a controlled experiment with a hypothesis (use create_experiment). The output is a JSON object, not a persisted record — save it on the client side if you need to reuse it. Governance: all MO§ES configurations carry the DEVELOPMENTAL label (for development use, not personnel performance rating) and the ASSOCIATION-not-CAUSATION evidence standard. Related tools: list_pilot_options (discover available options), validate_pilot_configuration (pre-deployment validation), create_experiment (pair config with a hypothesis).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "metrics": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Array of metric IDs to include (e.g., ['leverage', 'yield', 'token_snr', 'construction']). See list_pilot_options for the full catalog."
    },
    "cohort_size": {
      "type": "integer",
      "description": "Number of operators in the pilot cohort (e.g., 25, 50, 100). Determines statistical power and minimum detectable effect size."
    },
    "duration_days": {
      "type": "integer",
      "description": "Pilot duration in days (e.g., 30, 60, 90). Longer windows improve intervention re-evaluation stability."
    }
  }
}
    arguments 20 lines
  • assign_intervention unknown never probed

    Assign a targeted intervention to an operator. REQUIRES AUTHORIZATION. Contact [email protected] for pilot access.

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id",
    "intervention_type"
  ],
  "properties": {
    "notes": {
      "type": "string",
      "description": "Free-text notes about the intervention assignment"
    },
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001, op_003, op_034)"
    },
    "intervention_type": {
      "type": "string",
      "description": "Intervention type from catalog (e.g., prompt_template, context_window_expansion, model_switch)"
    }
  }
}
    arguments 21 lines
  • close_intervention unknown never probed

    Close an intervention with outcome notes and mark it complete. The intervention must exist and be active. Outcome notes should describe observed changes, unintended effects, and whether the target metric moved. After closing, the intervention is no longer eligible for verify_change comparisons. REQUIRES AUTHORIZATION — contact [email protected] for pilot access. In the synthetic demo, this returns an authorization notice. When to use: after an intervention period ends and you have outcome observations to record. When NOT to use: while an intervention is still active and being measured — use get_intervention_status to check the current state first. Behavioral transparency: on success, the intervention status transitions to 'closed' and a closed_at timestamp is recorded. On authorization failure (the demo behavior), the response includes error='AUTHORIZATION_REQUIRED', a human-readable message, and the tool name — no intervention state changes. Related tools: get_intervention_status (list active/closed interventions), verify_change (pre/post comparison for a closed intervention), assign_intervention (create a new intervention).

    mcp-tool

    {
  "type": "object",
  "required": [
    "intervention_id"
  ],
  "properties": {
    "outcome_notes": {
      "type": "string",
      "description": "Free-text notes about the intervention outcome — observed changes, unintended effects, whether the target metric moved"
    },
    "intervention_id": {
      "type": "string",
      "description": "Intervention ID to close (e.g., intv_001, intv_007). Must be an active intervention."
    }
  }
}
    arguments 16 lines
  • create_experiment unknown never probed

    Create an experiment configuration for controlled comparison studies. Experiments pair a pilot configuration with a hypothesis and measurement plan. Use create_pilot_configuration first to build the config, then pass it here. Experiments enforce the ASSOCIATION-not-CAUSATION evidence standard — controlled experiments may upgrade evidence to CAUSATION only with proper design (e.g., randomized assignment, pre-registered hypothesis, control group). REQUIRES AUTHORIZATION — contact [email protected] for pilot access. In the synthetic demo, this returns an authorization notice. When to use: when you need a controlled comparison (A/B test, before/after with control group, multi-arm trial across AI systems or intervention types). When NOT to use: for simple pre/post observations without a control group, use verify_change instead — it does not require authorization and returns an ASSOCIATION-labeled comparison. Behavioral transparency: on success, an experiment record is created with a unique experiment_id, initial status 'draft', and a created_at timestamp. On authorization failure (the demo behavior), the response includes error='AUTHORIZATION_REQUIRED', a human-readable message directing you to [email protected], and the tool name — no experiment record is created. Related tools: create_pilot_configuration (build the config to pass in), validate_pilot_configuration (pre-check the config), verify_change (lightweight pre/post without a full experiment).

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Experiment name (e.g., 'Q3 Claude vs ChatGPT operator comparison', 'Context window expansion pilot — Team Alpha')"
    },
    "configuration": {
      "type": "object",
      "description": "Pilot configuration object (JSON) — see list_pilot_options for available metrics, eval families, and benchmark classes. Can be generated by create_pilot_configuration."
    }
  }
}
    arguments 16 lines
  • record_workflow_observation unknown never probed

    Record a workflow fit observation linking an operator to a workflow stage with a fit score. Workflow fit measures how well an operator's AI usage patterns align with a specific workflow stage (e.g., debugging, code review, architecture). Fit scores range 0.0-1.0 where 1.0 indicates perfect alignment. Use get_workflow_fit to read existing observations. REQUIRES AUTHORIZATION — contact [email protected] for pilot access. In the synthetic demo, this returns an authorization notice. When to use: when you have observed an operator working in a specific workflow stage and want to record the fit score so it can be analyzed alongside other observations. When NOT to use: for reading existing workflow fit observations, use get_workflow_fit instead — it is read-only and does not require authorization. Behavioral transparency: on success, a new observation record is created with a unique observation_id and a recorded_at timestamp, echoing back the operator_id and workflow_id. On authorization failure (the demo behavior), the response includes error='AUTHORIZATION_REQUIRED', a human-readable message, and the tool name — no observation is recorded. Related tools: get_workflow_fit (read existing observations), get_operator_profile (operator metric profile used to compute fit).

    mcp-tool

    {
  "type": "object",
  "required": [
    "operator_id",
    "workflow_id"
  ],
  "properties": {
    "notes": {
      "type": "string",
      "description": "Free-text notes about the observation context — task type, AI system used, environmental factors"
    },
    "fit_score": {
      "type": "number",
      "description": "Workflow fit score from 0.0 (no alignment) to 1.0 (perfect alignment). Computed from operator metric profile vs workflow requirements."
    },
    "operator_id": {
      "type": "string",
      "description": "Pseudonymous operator ID (e.g., op_001, op_003, op_034)"
    },
    "workflow_id": {
      "type": "string",
      "description": "Workflow ID (e.g., wf_debugging, wf_code_review, wf_architecture, wf_refactor, wf_testing)"
    }
  }
}
    arguments 25 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/cfc5a9d0af66353f/badge.svg)](https://brick.blue/agent/cfc5a9d0af66353f)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.