All scored servers

Uptimeify: tool descriptions scored io.uptimeify/mcp-server

tools/list taken
(UTC)
Connected to
https://uptimeify.io/mcp
Scoring rules
v2
Score this URL as it is today

Scores, issues and names only

This page shows how Uptimeify (io.uptimeify/mcp-server)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/io.uptimeify/mcp-server
Average score
68.5 / 100Cloudy
Tools
20
Near-identical descriptions
0

Across the server

  • Minor
    The server has no instructions. Say there, once, what the server is for and when to use it: Claude Code and Gemini CLI read the instructions before the tool descriptions.instructions_missing

Tools

ip_geolocation

58 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

ping_test

58 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    It may be destructive, but destructiveHint is not set.destructive_unmarked

check_ssl

63 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

dmarc_check

63 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

domain_expiry

63 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context
  • Major
    It may be destructive, but destructiveHint is not set.destructive_unmarked

hsts_check

63 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

mx_lookup

63 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

port_check

63 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
8 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

asn_lookup

65 / 100Cloudy

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

reverse_dns

70 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
0 / 10

No issues.

website_status

70 / 100Clear

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

whois

70 / 100Clear

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

check_dns

75 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10

No issues.

dkim_check

75 / 100Clear

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

dns_propagation

75 / 100Clear

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

dnsbl_check

75 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10

No issues.

http_headers

75 / 100Clear

Purpose
17 / 20
When to use
5 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
5 / 10

No issues.

redirect_check

75 / 100Clear

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

response_time

75 / 100Clear

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

spf_check

75 / 100Clear

Purpose
17 / 20
When to use
0 / 20
Arguments
23 / 25
Return value
15 / 15
Constraints and side effects
10 / 10
Examples
10 / 10
  • Major
    Says nothing about when to use it, or when not to.no_usage_context

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers