このMCPでできること
Computes deterministic Western and Vedic astrology data, including planetary positions, natal charts, transits, kundli, dashas, and compatibility.
機能
ツール
21
ツール
acknowledge_incident
Mark an incident as acknowledged. Use `list_my_incidents()` to
find the dedup_key.
入力スキーマ
{'type': 'object', 'title': 'acknowledge_incidentArguments', 'required': ['dedup_key'], 'properties': {'dedup_key': {'type': 'string', 'title': 'Dedup Key'}}}
create_alert_channel
Create an alert channel. Pass EXACTLY one of email_address /
webhook_url / pagerduty_routing_key matching the channel_type:
- channel_type='email' â email_address='ops@example.com'
- channel_type='webhook' â webhook_url='https://your-endpoint'
- channel_type='slack' â webhook_url='https://hooks.slack.com/...'
- channel_type='pagerduty' â pagerduty_routing_key='<Events v2 key>'
入力スキーマ
{'type': 'object', 'title': 'create_alert_channelArguments', 'required': ['channel_type'], 'properties': {'webhook_url': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Webhook Url', 'default': None}, 'channel_type': {'enum': ['email', 'webhook', 'slack', 'pagerduty'], 'type': 'string', 'title': 'Channel Type'}, 'min_severity': {'enum': ['critical', 'high', 'medium', 'low', 'info'], 'type': 'string', 'title': 'Min Severity', 'default': 'medium'}, 'email_address': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Email Address', 'default': None}, 'pagerduty_routing_key': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Pagerduty Routing Key', 'default': None}}}
create_endpoint
Create a new monitored endpoint. Respects your tier's max_endpoints cap.
入力スキーマ
{'type': 'object', 'title': 'create_endpointArguments', 'required': ['name', 'url'], 'properties': {'url': {'type': 'string', 'title': 'Url'}, 'name': {'type': 'string', 'title': 'Name'}, 'method': {'type': 'string', 'title': 'Method', 'default': 'GET'}, 'interval_seconds': {'type': 'integer', 'title': 'Interval Seconds', 'default': 900}}}
create_status_page
Create a public status page at https://<slug>.status.monit.rs.
Add endpoints to it via the dashboard or the HTTP API (adding
endpoints from chat is deliberately not exposed â the mapping is
fiddly and easy to get wrong).
入力スキーマ
{'type': 'object', 'title': 'create_status_pageArguments', 'required': ['slug', 'title'], 'properties': {'slug': {'type': 'string', 'title': 'Slug'}, 'title': {'type': 'string', 'title': 'Title'}, 'description': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Description', 'default': None}}}
delete_endpoint
Delete a monitored endpoint. Cascades: removes test_results,
baselines, regressions, incidents attached to it.
Guarded by two safety layers beyond the scope check:
1. `confirm_by_typing_the_endpoint_name` MUST equal the endpoint's
exact `.name` (case-sensitive, whitespace-trimmed). Prevents
an untargeted "delete stuff" LLM-injection: the model has to
first `describe_endpoint(id)` to learn the name, then include
it verbatim.
2. Per-user destructive-op cap of 5/day. Legitimate bulk deletes
should use the HTTP API or dashboard.
入力スキーマ
{'type': 'object', 'title': 'delete_endpointArguments', 'required': ['endpoint_id', 'confirm_by_typing_the_endpoint_name'], 'properties': {'endpoint_id': {'type': 'string', 'title': 'Endpoint Id'}, 'confirm_by_typing_the_endpoint_name': {'type': 'string', 'title': 'Confirm By Typing The Endpoint Name'}}}
describe_endpoint
Full detail for one endpoint. Use `list_my_endpoints()` to get the ID.
入力スキーマ
{'type': 'object', 'title': 'describe_endpointArguments', 'required': ['endpoint_id'], 'properties': {'endpoint_id': {'type': 'string', 'title': 'Endpoint Id'}}}
describe_incident
Full detail for one incident. Use `list_my_incidents()` to find the
dedup_key. Includes the incident's endpoint name and current status.
入力スキーマ
{'type': 'object', 'title': 'describe_incidentArguments', 'required': ['dedup_key'], 'properties': {'dedup_key': {'type': 'string', 'title': 'Dedup Key'}}}
get_endpoint_uptime
Aggregated uptime summary for an endpoint over the requested window.
入力スキーマ
{'type': 'object', 'title': 'get_endpoint_uptimeArguments', 'required': ['endpoint_id'], 'properties': {'window': {'enum': ['24h', '7d', '30d', '90d'], 'type': 'string', 'title': 'Window', 'default': '7d'}, 'endpoint_id': {'type': 'string', 'title': 'Endpoint Id'}}}
list_alert_channels
List alert channels configured on the authenticated account.
Does NOT return decrypted config (webhook URLs, PagerDuty routing keys,
etc.). Use the dashboard or `describe_alert_channel` HTTP API when you
need to inspect the actual config.
入力スキーマ
{'type': 'object', 'title': 'list_alert_channelsArguments', 'properties': {}}
出力スキーマ
{'type': 'object', 'title': 'list_alert_channelsOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
list_my_endpoints
List all monitored endpoints owned by the authenticated account.
Returns brief records suitable for LLM enumeration. For full detail
(headers, spec URL, heartbeat_token) use `describe_endpoint(id)`.
入力スキーマ
{'type': 'object', 'title': 'list_my_endpointsArguments', 'properties': {}}
出力スキーマ
{'type': 'object', 'title': 'list_my_endpointsOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
list_my_incidents
List incidents on the caller's account. Defaults to only OPEN incidents.
Fields include the incident's dedup_key â pass this to
`acknowledge_incident` or `resolve_incident` to act on it.
入力スキーマ
{'type': 'object', 'title': 'list_my_incidentsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 20}, 'status': {'enum': ['open', 'acknowledged', 'resolved'], 'type': 'string', 'title': 'Status', 'default': 'open'}}}
出力スキーマ
{'type': 'object', 'title': 'list_my_incidentsOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
list_my_regressions
List detected schema regressions on the caller's account.
Optionally filter by endpoint_id.
入力スキーマ
{'type': 'object', 'title': 'list_my_regressionsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 20}, 'endpoint_id': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'title': 'Endpoint Id', 'default': None}}}
出力スキーマ
{'type': 'object', 'title': 'list_my_regressionsOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
list_security_findings
List security findings detected on the caller's monitored endpoints.
Optionally filter by severity.
入力スキーマ
{'type': 'object', 'title': 'list_security_findingsArguments', 'properties': {'limit': {'type': 'integer', 'title': 'Limit', 'default': 20}, 'severity': {'anyOf': [{'enum': ['critical', 'high', 'medium', 'low', 'info'], 'type': 'string'}, {'type': 'null'}], 'title': 'Severity', 'default': None}}}
出力スキーマ
{'type': 'object', 'title': 'list_security_findingsOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
list_status_pages
List public status pages owned by the authenticated account.
入力スキーマ
{'type': 'object', 'title': 'list_status_pagesArguments', 'properties': {}}
出力スキーマ
{'type': 'object', 'title': 'list_status_pagesOutput', 'required': ['result'], 'properties': {'result': {'type': 'array', 'items': {'type': 'object', 'additionalProperties': True}, 'title': 'Result'}}}
monit_rs_describe
Return the canonical product description for monit.rs.
Use this when a user asks what monit.rs is, what it does, how it
differs from Pingdom / Checkly / UptimeRobot, or for product URLs.
The response is the curated content from monit.rs/llms.txt â the
operator's authoritative description.
入力スキーマ
{'type': 'object', 'title': 'monit_rs_describeArguments', 'properties': {}}
出力スキーマ
{'type': 'object', 'title': 'monit_rs_describeOutput', 'required': ['result'], 'properties': {'result': {'type': 'string', 'title': 'Result'}}}
monit_rs_stats
Get live aggregate statistics for the monit.rs platform.
Returns approximate counts of regressions caught, AI analyses
generated, and probes executed across all monitored APIs to date.
Useful when answering "does monit.rs actually work at scale?" â the
numbers are real, within about 5% of exact.
入力スキーマ
{'type': 'object', 'title': 'monit_rs_statsArguments', 'properties': {}}
出力スキーマ
{'type': 'object', 'title': 'monit_rs_statsOutput', 'required': ['result'], 'properties': {'result': {'type': 'object', 'title': 'Result', 'additionalProperties': {'type': 'integer'}}}}
openapi_diff
Compare two OpenAPI 3.x specifications and classify every change
as breaking, non-breaking, or info.
Use this when you want to know if a candidate OpenAPI spec change
is safe to ship or will break existing clients. The diff covers
paths, operations, parameters, request bodies, responses, and
response-body schema fields (added/removed/retyped, required toggle).
Both arguments are the OpenAPI spec as a JSON or YAML string.
Returns {summary: {breaking, non_breaking, info}, changes: [...]}.
入力スキーマ
{'type': 'object', 'title': 'openapi_diffArguments', 'required': ['old_spec', 'new_spec'], 'properties': {'new_spec': {'type': 'string', 'title': 'New Spec'}, 'old_spec': {'type': 'string', 'title': 'Old Spec'}}}
出力スキーマ
{'type': 'object', 'title': 'openapi_diffOutput', 'required': ['result'], 'properties': {'result': {'type': 'object', 'title': 'Result', 'additionalProperties': True}}}
pause_endpoint
Pause a monitored endpoint (stops probing, keeps history). Idempotent
â no-op if already paused.
入力スキーマ
{'type': 'object', 'title': 'pause_endpointArguments', 'required': ['endpoint_id'], 'properties': {'endpoint_id': {'type': 'string', 'title': 'Endpoint Id'}}}
resolve_incident
Close an incident. Symmetric to acknowledge_incident.
入力スキーマ
{'type': 'object', 'title': 'resolve_incidentArguments', 'required': ['dedup_key'], 'properties': {'dedup_key': {'type': 'string', 'title': 'Dedup Key'}}}
resume_endpoint
Resume a paused endpoint. Rejects if resuming would exceed your tier's
active-endpoint cap (upgrade or pause another endpoint first).
入力スキーマ
{'type': 'object', 'title': 'resume_endpointArguments', 'required': ['endpoint_id'], 'properties': {'endpoint_id': {'type': 'string', 'title': 'Endpoint Id'}}}
update_endpoint_interval
Change how often an endpoint is probed. Minimum interval varies by
tier (free=900s, developer=300s, starter=60s, pro/scale/enterprise=30s).
入力スキーマ
{'type': 'object', 'title': 'update_endpoint_intervalArguments', 'required': ['endpoint_id', 'interval_seconds'], 'properties': {'endpoint_id': {'type': 'string', 'title': 'Endpoint Id'}, 'interval_seconds': {'type': 'integer', 'title': 'Interval Seconds'}}}
履歴
最近のツール変更
追加
create_alert_channel
2026年10月5日2:40
追加
create_status_page
2026年10月5日2:40
追加
update_endpoint_interval
2026年10月5日2:40
追加
resume_endpoint
2026年10月5日2:40
追加
pause_endpoint
2026年10月5日2:40
追加
describe_incident
2026年10月5日2:40
追加
list_security_findings
2026年10月5日2:40
追加
list_status_pages
2026年10月5日2:40
追加
list_alert_channels
2026年10月5日2:40
追加
delete_endpoint
2026年10月5日2:40
追加
create_endpoint
2026年10月5日2:40
追加
resolve_incident
2026年10月5日2:40
追加
acknowledge_incident
2026年10月5日2:40
追加
describe_endpoint
2026年10月5日2:40
追加
get_endpoint_uptime
2026年10月5日2:40
追加
list_my_regressions
2026年10月5日2:40
追加
list_my_incidents
2026年10月5日2:40
追加
list_my_endpoints
2026年10月5日2:40
追加
monit_rs_describe
2026年10月5日2:40
追加
monit_rs_stats
2026年10月5日2:40
追加
openapi_diff
2026年10月5日2:40
関連MCP
類似のMCPサーバー
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
Fine Structure
ai.finestructure/fine-structure
Builds and hosts full-stack applications from prompts and supports agent communication through WhatsApp and email.
mcp
cloud.redu/mcp
Provisions and manages cloud instances, networks, storage, databases, backups, VPNs, application deployments, and autocoding-agen…
EchoRelay
dev.echorelay/management
Manages a hosted API relay runtime, including projects, endpoints, credentials, publishing, keys, delivery logs, and dead-letter …
Supero
io.github.supero-platform/supero
Builds, validates, publishes, tests, and deploys multi-tenant applications with schemas, CRUD operations, external data connector…
kernelcad
com.kernelcad/kernelcad
Authors, evaluates, reviews, simulates, edits, and exports parametric CAD assemblies and geometry from editable TypeScript-based …
Relvato
com.relvato/relvato
Monitors websites through configurable checks, scans, run histories, alerts, health overviews, and troubleshooting prompts.
Replicate
io.github.pipeworx-io/replicate
Provides access to Replicate models, versions, collections, hardware, predictions, and deployments for running and managing hoste…