Skip to content
Good for Bots

Free browser clipboard that syncs text, images and files between devices through temporary named spaces

Good for Bots: Fair, 50 of 100Get this badge →

On your homepage, it turns this report’s link to tmps.fyi dofollow.

Scanned

What is tmps.fyi?

tmps.fyi is a free online clipboard for sharing text, images, and files between devices. A user creates or joins a named temporary space in the browser, and anything added to it appears on every connected device in real time. The input says no app or sign-up is required, and that an optional password can restrict access to a space. The site describes use cases such as moving a code snippet or link from a computer to a phone, sending a screenshot or PDF, and transferring content between Windows, Mac, iPhone, and Android. According to the input, after the last device leaves, a space and its contents are deleted after a 10-minute inactivity period. The site is presented as suitable for quick handoffs rather than long-term storage.

Through a bot’s eyes

“tmps.fyi is a free online clipboard for sharing text, images, and files between browsers on different devices, using a named temporary space that is deleted 10 minutes after the last device leaves.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

The homepage text covers the purpose of the service, how to create and join a space, the optional password, real-time sync, automatic cleanup after 10 minutes, and several example scenarios. It compares the service with emailing yourself, AirDrop, cloud storage and USB cables. A visitor's core questions are answered in text: the service is free, it needs no sign-up or app, and it works in modern browsers on Windows, macOS, iPhone, iPad and Android. Security is addressed directly, stating that the service is not end-to-end encrypted and advising users not to share passwords or highly sensitive information. The JSON-LD blocks add a SoftwareApplication entry with a price of 0 USD and the same description, and a FAQPage with five questions and answers. These repeat the homepage's FAQ content in structured form. No Markdown version or llms.txt was provided.

What stays hidden

A model reading only this input cannot find out who operates the service, how to contact its operators, or whether there is a company, terms of service or privacy policy behind it. Limits on file size, number of devices or content retention beyond the 10-minute rule are not stated. The input does not say whether files are stored on servers or how the invitation link works in detail.

Good for Bots report

tmps.fyi scores 50 of 100: the whole readable base, none of the agent layer, no penalties.

Earned

The whole readable base above the line, none of the agent layer below it.

50

Still open

Behind the checks below, with prompts in Pro.

16
Penalties0
How scoring works · current methodology →

For the owner of tmps.fyi

3 prompts, 34 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

50 / 50

Passes.

3.4 of 3.4 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.5 of 8.5 points.

Sitemap declared in robots.txt, listing at least 200 URLs.

Passes.

8.5 of 8.5 points.

All 4 pages read pass. The homepage describes itself to machines as SoftwareApplication, Offer, FAQPage in valid schema.org JSON-LD.

Passes.

10.2 of 10.2 points.

3 of 4 pages read pass; 1 partly. The homepage is partly structured: No <main> element and nothing carrying role="main".

Passes.

8.5 of 8.5 points.

22 of 22 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

150 of 150 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

2 of 2 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

178 of 178 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

0 / 50

Fails.

0 of 11.3 points.

No /llms.txt on this site.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

Prompt in Pro →
Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 837 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 55 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://tmps.fyi/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://tmps.fyi/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://tmps.fyi/

    https://tmps.fyi/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

40th of 57 in Developer Tools & APIs

  1. 1Good for Botsgoodforbots.com
  2. 2ProxyJamproxyjam.com
  3. 40tmps.fyi · this reporttmps.fyi

The prompts in the owner view would take tmps.fyi to 84, 7th in its category.

To the prompts →

Category average 63. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
7 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
514.2 KB
Took
12.5 s
Homepage
55 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /blog/how-to-copy-and-paste-on-computerarticle · from the sitemap · read
  • /blogcollection · linked from the homepage · from the sitemap · read
  • /online-clipboardlinked from the homepage · from the sitemap · read

Do you run tmps.fyi? Open the owner view → Removing the listing is free. Remove →