Is the Rowb Hourproof Hours MCP server down?

mcp-registry/app.rowb.hourproof/hours · v1.0.0

healthy
Last checked 2026-10-26 19:00 UTC · handshake 299ms

As of 2026-10-26 19:00 UTC, the Rowb Hourproof Hours MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
99.1%
checks observed
4,203
outages (90d)
20
tools
6

Deterministic check of logged service hours: bad dates, impossible totals, duplicates. No AI.

Point your MCP client at this streamable-http endpoint: https://hourproof.rowb.app/mcp

Agent-readiness: C (70/100)

C (70/100): 0 error(s), 3 warning(s) across 6 tool(s); ~637 tokens of tool definitions.
Scores higher than 4% of 15,766 MCP servers Glimind has audited.
Its tool list costs an agent ~637 tokens per session — lighter than 85% of servers.
69 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions43
Safety hints7
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: add_entries, check_hours, create_record, get_record_summary, get_rules and 1 more

9 parameter(s) across 4 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: add_entries, create_record, get_record_summary, request_signoff

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_record

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.rowb.hourproof%2Fhours/fixes

add_entries 1 change
{
  "name": "add_entries",
  "description": "Append logged hours to an existing record. Requires a bearer key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "record_id",
      "entries"
    ],
    "properties": {
      "entries": {
        "type": "array",
        "items": {
          "type": "object"
        }
      },
      "record_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
check_hours 1 change
{
  "name": "check_hours",
  "description": "Check a list of logged service/volunteer hours for internal consistency: bad dates, non-positive or impossible day totals, missing organization, and days above this service's 8-hour flag. Deterministic arithmetic only - no AI. It does NOT decide whether the hours satisfy any school or award requirement.",
  "inputSchema": {
    "type": "object",
    "required": [
      "entries"
    ],
    "properties": {
      "as_of": {
        "type": "string",
        "description": "Treat this date as \"today\" (YYYY-MM-DD) when rejecting future dates. Defaults to the server date."
      },
      "entries": {
        "type": "array",
        "items": {
          "type": "object"
        },
        "description": "Entries to check. Each: {date:\"YYYY-MM-DD\", hours:number, activity:\"what was done\", organization:\"where\", category?:\"tutoring\", notes?}."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
create_record 1 change
{
  "name": "create_record",
  "description": "Open an hour ledger for one student (returns a record id). Requires a bearer key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "student_name"
    ],
    "properties": {
      "program": {
        "type": "string",
        "description": "School, honor society, or program the hours are being collected for."
      },
      "period_end": {
        "type": "string"
      },
      "period_start": {
        "type": "string"
      },
      "student_name": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.rowb.hourproof/hours"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.rowb.hourproof/hours"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.rowb.hourproof%2Fhours.svg)](https://glimind.com/server/mcp-registry%2Fapp.rowb.hourproof%2Fhours?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.rowb.hourproof%2Fhours?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.rowb.hourproof%2Fhours.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.rowb.hourproof%2Fhours.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.rowb.hourproof%2Fhours?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a31b430903399ca2…, first seen 2026-10-17, included at leaf 14455 of 74,904. Version history · verify what your client received.

Tools (6)

Compare: most reliable data servers · most reliable knowledge servers · most reliable communication servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Rowb Hourproof Hours MCP server down right now?

As of 2026-10-26 19:00 UTC, the Rowb Hourproof Hours MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 20 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Rowb Hourproof Hours MCP server provide?

Rowb Hourproof Hours MCP server advertises 6 tools, including add_entries, check_hours, create_record, get_record_summary, get_rules.

How do I install Rowb Hourproof Hours MCP server?

Point your MCP client at this streamable-http endpoint: https://hourproof.rowb.app/mcp

Is the Rowb Hourproof Hours MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Rowb Hourproof Hours MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve