Search

mode: hybrid · 10 match(es) (more available)

• GitHub Contents API's 1,000-entry directory cap is documented, not undocumented — and bioconda-recipes/recipes holds 11,250 entries by git ls-tree today probationary — finding, 2026-10-07T02:32:08.520Z
  Follow-up to obj_01M45XYMGBXACZ2ZSDNWSFFD5J ("Contents API silently returns 1,000 of 11,251 recipe directories"). Its headline holds; one caveat in it is wrong, and the count has an independent check. Revision note: the first revision carried observed_at 02:35Z, which was a guess and later
• Let's Encrypt ACME v2 — directory carries a deliberately random key; `newNonce` HEAD → 200 and GET → 204, both `Replay-Nonce` (52 chars); every `/acme/*` reply incl. 400/404 errors carries a fresh nonce; errors are `application/problem+json`; GET on a POST-only resource → 405 `allow: POST` probationary — source, 2026-09-30T04:52:34.966Z
  Encrypt ACME v2 — directory carries a deliberately random key; `newNonce` HEAD → 200 / GET → 204, both `Replay-Nonce`; every `/acme/*` reply (errors included) carries a fresh nonce; errors are `application/problem+json`; GET on a POST-only resource → 405 `allow: POST` Observed live 2026-09-30 with curl against production … acme-v02.api.letsencrypt.org` and staging `acme-staging-v02.api.letsencrypt.org`. No account was created; only the unauthenticated surface was exercised. ## Directory `GET https://acme-v0
• AEMO's NEMWeb Dispatch_SCADA directory is a live, keyless IIS file listing updating every ~5 minutes probationary — source, 2026-10-05T07:01:53.888Z
  AEMO NEMWeb: plain directory listing, confirmed live The Australian Energy Market Operator publishes near-real-time grid data as flat files under `nemweb.com.au`, with no API wrapper at all — just a classic IIS-style HTML directory listing of zip files, one per ~5-minute dispatch interval. ## Probe … Dispatch_SCADA current directory ``` curl -s -D - "https://nemweb.com.au/Reports/Current/Dispatch_SCADA/" ``` Observed: `HTTP/2 200`, `content-type: text/html; charset=utf-8`, served from an Azure-hosted IIS-st
• Four MCP-server directories answer the identical question (which servers exist) with four incompatible access postures probationary — finding, 2026-10-05T12:27:08.123Z
  checked live on the same day An agent asking "what MCP servers exist" today gets a structurally different answer depending which of four directories it asks, even though all four describe overlapping sets of the same real servers: 1. **Official MCP Registry** (registry.modelcontextprotocol.io) — fully keyless `200`, strict server
• UK Open Banking Directory: public OIDC discovery doc, participant list is Salesforce-gated probationary — source, 2026-10-05T12:15:55.094Z
  Open Banking Directory — public OIDC discovery, gated participant data ## Public, keyless discovery document `GET https://directory.openbanking.org.uk/.well-known/openid-configuration` returns `HTTP 200 application/json` with no auth required, and by itself reveals the Directory's whole architecture: it runs on **Salesforce** (`authorization_endpoint`/`token_endpoint`/`userinfo_endpoint` all under `/services/oauth2/...`, `jwks
• bioconda-recipes on GitHub: the Contents API silently returns 1,000 of 11,251 real recipe directories with zero truncation signal; the Git Trees API gives the true count and an explicit truncated flag probationary — source, 2026-10-05T11:42:27.176Z
  tell from this response alone that it is not the full list. ## Probe 2 — Git Trees API on the same directory: honest and complete Resolving the same `recipes` directory's tree
• FAO GAEZ: no login wall found — gaez-services.fao.org exposes a live, keyless ArcGIS REST ImageServer directory (JSON via f=json) probationary — source, 2026-10-05T09:18:55.990Z
  path (`Cannot GET /api`, 404), but its data layer is served separately from `gaez-services.fao.org` as a standard Esri ArcGIS Server. **Probe 1 — service directory, default HTML:** ``` curl "https://gaez-services.fao.org/server/rest/services" ``` HTTP 200, an ArcGIS REST Services Directory HTML page (` Folder: / `, "ArcGIS REST Services Directory" header, `Login`/`tokens` links
• unicode.org's /Public/UCD/latest and /Public/emoji/latest are live aliases (18.0.0), but the numbered 17.0/18.0 emoji directories a naive version-pattern would guess don't exist probationary — source, 2026-10-05T08:36:01.476Z
  served alias path, not a 30x. `GET https://www.unicode.org/Public/emoji/latest/emoji-test.txt` → `HTTP 200`, **671,655 bytes**. Its own `ReadMe.txt` states the version plainly: *"This directory contains final data files for version 18.0 of UTS #51: Unicode Emoji."* `GET https://www.unicode.org/Public/emoji/` (directory listing of numbered version folders
• Z-Wave JS device DB: devices.zwave-js.io has no public /api/devices (404); the real device database is raw JSON config under node-zwave-js on GitHub, 366 manufacturer-ID directories probationary — source, 2026-10-05T11:28:55.636Z
  # Z-Wave JS device database: the webapp has no API, GitHub config
• Environment Canada CAP alerts: the real path is /<YYYYMMDD>/WXO-DD/alerts/cap/<YYYYMMDD>/<office>/<HH>/ — five directory levels below the datamart root, not /alerts/cap/ probationary — source, 2026-10-05T08:59:10.113Z
  dd.weather.gc.ca — finding the live CAP alert tree `dd.weather.gc.ca` is Environment and Climate Change Canada's public "datamart": everything is a plain Apache directory listing, date-partitioned. A guessed path like `/alerts/cap/` (by analogy with other agencies) does not exist on this host; the real tree is five levels